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/firatcand/forge/auditnpx skills add firatcand/forge --skill auditgit clone --depth 1 https://github.com/firatcand/forgeWrote 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/firatcand/forge/audit)<a href="https://agentmods.dev/skills/firatcand/forge/audit"><img src="https://agentmods.dev/badge/skills/firatcand/forge/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.00062 | $0.01613 |
| Opus 5 | $0.00031 | $0.00807 |
| Sonnet 5 | $0.00012 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00161 |
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 3d ago.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit
READ-ONLY. This skill produces a work-order of audit findings — it NEVER edits, creates, or deletes source. The only file it writes is the work-order under
.forge/audits/<ts>/. No self-loop.
The user-facing audit driver. One invocation = one audit pass:
audit plan(read-only) → parse the per-(scope × dimension) prompts.- Fan out one read-only Task subagent per prompt; each returns findings JSON.
- Assemble all findings →
audit collect→ filtered, validated work-order. - Present the work-order (counts + path) and the read-only guarantee.
- Offer the next step (NOT built here): turning approved findings into issues.
Preconditions
- A git repo (scope auto-discovery ranks tracked dirs; a non-git repo falls back
to scope
["**"]with a warning). .forge/settings.yamlis OPTIONAL — when absent, audit uses defaults and warns (verify unconfigured). The protected set comes from the adopter-curatedCRITICAL.md+settings.audit.protected_globsONLY; scope comes fromsettings.audit.scope_globsor git-tree auto-discovery. You never hardcode paths, and the JS-flavoredagents.preflight_globsdefault is NOT folded in (it would leak forge-shaped paths into a non-forge repo's audit).
Step 1 — Plan the audit (read-only, writes nothing)
forge orchestrate audit plan --json
Parse data:
prompts[]— each{ scope, dimension, prompt }. Thepromptis a complete, self-contained read-only audit instruction (it already embeds the scope glob, the dimension focus, the protected globs to avoid, the finding schema, the 6-way classification rubric, the per-agent cap, and the read-only mandate).scope,dimensions,protected_globs— the resolved sets.verify_configured— whenfalse, surface the warning: findings are UNVERIFIABLE without averify:gate; the audit must be paired with one.warnings[]— scope-fallback / settings-absent notices to relay.
Optional overrides: --scope a/**,b/** and --dimensions dead-code,duplication.
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.
- 3d ago First seen · 142 lines · 62 tokens per session scan A 7f78132492f9
audit is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,613 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-08-30.
Other skills, from other repositories
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
prospec-knowledge-generate
Generate AI Knowledge - Read raw-scan.md, analyze project structure, autonomously decide module boundaries, and produce Recipe-First module READMEs and index. Triggers: generate knowledge, analyze project, module split, 產生知識, 知識庫, 分析專案, 模組拆分.
submit-pr
Open a prospec pull request in the house format — push the change's two commits, write the Traditional Chinese body, and link it to its issue. Triggers: submit pr, open pr, 開 PR, 送 PR, 發 PR, pull request, 提交 PR.
submit-issue
Open a prospec GitHub issue in the house format — conventional-commit title, Traditional Chinese body (problem → solutions → acceptance criteria), downstream-compatibility block, series cross-links, and optional model-routing guidance. Triggers: submit issue, open issue, create issue, file issue, 開 issue, 發 issue, 建…
prospec-explore
Explore - Requirement exploration, problem investigation, and solution comparison partner. Triggers: explore, compare, investigate, unsure, clarify, 探索, 比較, 釐清, 調查, 不確定.
prospec-plan
Plan Implementation - Convert User Story into technical implementation plan (plan.md) and change specification (delta-spec.md). Triggers: plan, architecture, technical plan, 規劃, 架構規劃, 技術規劃.