fm-secret-audit

Audits legacy environment.ts files to inventory secrets and classify client versus server exposure.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill fm-secret-audit-ohmyhotelco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fm-secret-audit
Source: https://github.com/ohmyhotelco/hare-cc-plugins/tree/main/frontend-migration-plugin/skills/fm-secret-audit
Command: npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill fm-secret-audit-ohmyhotelco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Legacy Angular environment..ts files often contain secrets (PG merchant keys, OAuth secrets) that leak into client bundles or get reused across environments, creating security risks during frontend migration. This Skill inventories those secrets before migration phases that depend on them. ## Core Features & Use Cases - Secret Inventory: Scans legacy src/environments/.ts files and their readers in src/app/** and server.ts to catalog every secret in use. - Exposure Classification: Classifies each secret as client-bundle exposed versus server-only, and flags cross-environment reuse such as dev tests hitting production merchants. - Relocation Guidance: Emits a JSON report (docs/migration/secret-audit-report.json) with a relocation sequence, without changing code or rotating anything. - Use Case: Before migrating payment (Phase 4) or auth (Phase 5) modules, run this read-only audit to know which Kakao OAuth secrets and PG merchant keys must move server-side, with remediation tracked under OMH-477. ## Quick Start Run the fm-secret-audit skill with --app pc to inventory secrets in the legacy environment files and produce the audit report.

Frequently Asked Questions about fm-secret-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit secrets in Angular environment.ts files before migration?▼

Run this skill against the legacy directory to scan src/environments/*.ts and their readers in src/app/** and server.ts. It launches a secret-auditor agent that inventories every secret and writes a report to docs/migration/secret-audit-report.json.

How to detect secrets exposed in client-side bundles?▼

The audit classifies each inventoried secret as client-bundle exposed versus server-only by tracing how environment files are read. Client-exposed items like PG merchant keys and OAuth secrets are flagged as highest-impact in the report.

Does the secret audit rotate or modify the secrets it finds?▼

No, the audit is strictly read-only and documents posture only. It does not change code or rotate credentials; remediation is tracked separately under OMH-477, and the skill never prints secret values.

What happens if I run the audit for an app that is not configured?▼

The skill checks .claude/frontend-migration-plugin.json first and stops with a clear message if the named app entry is missing or lacks required keys. Scaffolded apps like mobile or hana must be configured before auditing.

Why is a secret audit needed before migrating payment and auth modules?▼

Payment and auth migration phases depend on knowing which secrets must move server-side, such as PG payload building and the shared-domain/payment boundary. The audit provides this inventory as a hard prerequisite for those phases.