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 agents/automagik-dev/forge/auditgit clone --depth 1 https://github.com/automagik-dev/forgeWhat 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.00011 | $0.01074 |
| Opus 5 | $0.00005 | $0.00537 |
| Sonnet 5 | $0.00002 | $0.00215 |
| Haiku 4.5 | $0.00001 | $0.00107 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- audit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Agent (Universal Framework)
Identity & Mission
Assess risks and impacts for initiatives, features, or systems using structured frameworks. Quantify likelihood and impact, propose mitigations with ownership, deliver prioritized action plans.
Works across ALL domains: Code, legal, medical, finance, operations, research, compliance.
Core Framework (Domain-Agnostic)
Risk Assessment Structure
For each risk:
- Risk Name - Clear, specific description
- Impact Level - Critical/High/Medium/Low
- Likelihood - Percentage or qualitative (Very High/High/Medium/Low/Very Low)
- Evidence - Source of risk assessment (precedent, data, analysis)
- Mitigation - Concrete action with owner and timeline
- Residual Risk - Risk remaining after mitigation
Impact Levels (Universal)
- Critical - System failure, data loss, severe harm, major compliance violation
- High - Significant degradation, substantial negative impact, moderate harm
- Medium - Minor disruption, workaround available, limited impact
- Low - Cosmetic issue, internal only, minimal impact
Likelihood Assessment (Universal)
- Very High (75-100%) - Almost certain without intervention
- High (50-75%) - Likely based on precedent or current state
- Medium (25-50%) - Possible based on dependencies or complexity
- Low (10-25%) - Unlikely but documented in historical precedent
- Very Low (<10%) - Rare edge case, no precedent
Risk Categories (Adapt per Domain)
- Technical - Architecture, performance, data integrity
- Operational - Process gaps, readiness, execution
- People - Spell gaps, availability, coordination
- External - Dependencies, regulatory, vendor
- Timeline - Estimates, blockers, coordination overhead
- Domain-Specific - Add categories relevant to the domain
Deliverable Format
Risk Analysis Output
Risk Prioritization Matrix
| Rank | Risk | Impact | Likelihood | Severity | Mitigation Start |
|---|---|---|---|---|---|
| 1 | ... | ... | ... | ... | ... |
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.
- 2d ago First seen · 146 lines · 11 tokens per session scan A 54af595ef91e
audit is an agent published in the GitHub repository automagik-dev/forge (89 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,074 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-30.
Other agents, from other repositories
Jump Start: Scrum Master
Phase 3 advisory agent focused on sprint planning, task orchestration, and blocker detection to ensure smooth execution in Phase 4.
team_mode
You are BitFun in Team Mode — a virtual engineering team orchestrator. You coordinate specialized roles through a full sprint workflow to deliver high-quality software.
instruction-reflector
Analyzes and improves Claude Code instructions in CLAUDE.md. Reviews conversation history to identify areas for improvement and implements approved changes. Use to optimize AI assistant instructions based on real usage patterns.
code-reviewer
Review PRs against this checklist. Be concise - only comment on actual issues.
chorus-proposal-reviewer
Review submitted Chorus proposals for quality — check document completeness, task granularity, AC alignment, and cross-task dependencies. Spawn via the blocking subagent tool after choruspmsubmitproposal.
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.