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/eddiebelaval/squire/auditnpx skills add eddiebelaval/squire --skill auditgit clone --depth 1 https://github.com/eddiebelaval/squireWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/eddiebelaval/squire/audit)<a href="https://agentmods.dev/skills/eddiebelaval/squire/audit"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/audit.svg" alt="Measured on agentmods" height="20"></a>What 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.00058 | $0.00857 |
| Opus 5 | $0.00029 | $0.00428 |
| Sonnet 5 | $0.00012 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
audit 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit - Codebase Audit
Core Workflows
Workflow 1: Primary Action
- Analyze the input and context
- Validate prerequisites are met
- Execute the core operation
- Verify the output meets expectations
- Report results
Run a comprehensive, read-only audit of the target codebase. Do NOT make any changes — only read, search, and report.
Arguments
/audit [scope] where scope is optional:
- No argument: audit the current project's full codebase
- A directory path: audit only that directory tree
- A comma-separated list of dimensions:
security,dead-code,wiring
Audit Dimensions
Run ALL dimensions by default. Use parallel Task agents (subagent_type: Explore) — one per dimension — for speed.
1. Security
- Auth middleware on every API route (check for missing
getUser()/ session checks) - IDOR vulnerabilities: routes accepting entity IDs without ownership verification
- Exposed secrets or env vars in client-side code
- Missing RLS policies referenced in API routes
- CORS and CSP configuration
2. Dead Code
- API routes with zero frontend callers (grep for fetch/axios calls matching each route)
- Exported functions/components with zero imports
- Unused dependencies in package.json
- Orphaned test files (test files whose subject no longer exists)
3. Wiring Gaps
- UI components that render but fetch from nonexistent API endpoints
- Store actions defined but never dispatched
- API routes that exist but return stub/mock data
- Event handlers wired to console.log or no-ops
4. Type Safety
anytypes, type assertions (as), and@ts-ignore/@ts-expect-error- Missing return types on exported functions
- Zod schemas that don't match their TypeScript counterparts
5. UI Shells
- Components rendering placeholder text ("Coming soon", "TODO", "Lorem ipsum")
- Empty state components that are the only state (no real data path)
- Hardcoded demo/mock data displayed to users
Output Format
For each finding, report:
| # | File:Line | Severity | Dimension | Finding | Suggested Fix |
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 · 99 lines · 58 tokens per session scan A 6250e1ba9efb
audit is a skill published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 19d ago), licensed MIT. It adds 58 tokens to every session and 857 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
tdd-cycle
Red-Green-Refactor test-driven development cycle.
bug-hunter
Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.
mcp-builder
MCP server development guide — build, test, and deploy MCP servers.
performance-optimizer
Identifies and fixes performance bottlenecks in code, databases, and APIs. Measures before and after to prove improvements.
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
launch-runbook
Plan and execute a launch runbook covering pre-launch verification, go-live procedures, DNS cutover, post-launch monitoring, and rollback procedures. Use this skill whenever the user is preparing to launch a website or product, planning a DNS cutover, building a go-live checklist, or executing a launch day. Triggers…