Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/random6913/claude-code-superkit/audit-frontendnpx skills add RaNDoM6913/claude-code-superkit --skill audit-frontendgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00026 | $0.00892 |
| Opus 5 | $0.00013 | $0.00446 |
| Sonnet 5 | $0.00005 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
audit-frontend scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Audit
Audit frontend source code for code quality issues, hardcoded values, dead code, and pattern violations.
Detection Strategy
Auto-detect frontend projects by scanning for:
package.jsonwith React/Vue/Svelte/Angular dependenciestsconfig.jsonfor TypeScript projectssrc/directory structure
Identify all frontend directories (there may be multiple — e.g., user-facing app + admin panel).
Checks
1. Hardcoded Values in State
Grep useState.*["'][A-Z]|useState.*["'][a-z]{3,} for hardcoded initial state values.
FAIL if personal data (names, emails, phone numbers) used as defaults — should come from API/props.
2. Placeholder Image URLs
Grep unsplash\.com|picsum\.photos|pravatar\.cc|placeholder\.com|placehold\.co|via\.placeholder.
FAIL if used as production defaults without API fallback.
3. Mock Data in Production Code
Grep MOCK_|mockData|mock://|const mock[A-Z] in page/component files (NOT in dedicated test/mock files).
FAIL for mock arrays or objects in production page components.
4. console.log/debug/info
Grep console\.(log|debug|info) in source files. Exclude console.error and console.warn.
WARN with file count and locations.
5. TypeScript Strict Compliance
Run npx tsc --noEmit in each frontend project directory.
FAIL for any type errors.
Also grep for as any|: any — WARN with count (indicates type safety gaps).
6. Dead Imports
Grep for imports from files that no longer exist:
# Check for broken imports by running TypeScript compiler
npx tsc --noEmit 2>&1 | grep "Cannot find module"
FAIL if importing deleted or non-existent files.
7. Design Token Compliance
Grep #[0-9a-fA-F]{3,8} in component/page files (NOT in token/theme definition files).
WARN for hardcoded color values that should reference design tokens.
Also check for hardcoded spacing (margin:\s*[0-9]+px|padding:\s*[0-9]+px) outside utility classes.
8. Query Key Centralization
If using TanStack Query/React Query, grep useQuery.*queryKey:\s*\[['"] for inline string array keys.
WARN if not using a centralized query key factory.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 93 lines · 26 tokens per session scan A 8f9bb123563b
audit-frontend is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 892 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…