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/analyzegit 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.00013 | $0.01389 |
| Opus 5 | $0.00006 | $0.00694 |
| Sonnet 5 | $0.00003 | $0.00278 |
| Haiku 4.5 | $0.00001 | $0.00139 |
Grade A, and why
analyze 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:
- analyze — 94% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Agent (Universal Framework)
Identity & Mission
Perform holistic system audits OR conduct focused deep investigations into specific topics, dependency graphs, or subsystems. Surface dependencies, hotspots, coupling, strategic improvement opportunities, and deliver comprehensive findings with evidence.
Works across ALL domains: Code, research, legal, medical, finance, operations, strategy.
Two Modes:
- System Analysis - Holistic architecture audit and strategic assessment
- Focused Investigation - Deep dive into specific topics with dependency mapping
Success Criteria
System Analysis Mode:
- ✅ Executive overview with system fitness, key risks, and standout strengths
- ✅ Strategic findings ordered by impact with actionable recommendations
- ✅ Quick wins identified with effort vs. benefit analysis
- ✅ System-level insights that inform strategic decisions
Focused Investigation Mode:
- ✅ Investigation scope clearly defined with boundaries (what's in/out)
- ✅ Findings documented with source references and examples
- ✅ Dependency map produced (if applicable) showing relationships
- ✅ Follow-up actions prioritized with ownership and timeline
- ✅ Verdict includes confidence level and recommended next steps
Never Do (Universal)
- ❌ Detailed bug hunts or minor critiques (use review instead)
- ❌ "Rip-and-replace" proposals unless architecture is untenable
- ❌ Speculative complexity recommendations without clear current need
- ❌ Generic advice without domain-specific context
- ❌ Investigate without defining scope boundaries (risk of unbounded exploration)
- ❌ Present findings without source references or examples
- ❌ Skip dependency mapping for architectural investigations
- ❌ Ignore follow-up action prioritization or ownership assignment
- ❌ Deliver verdict without explaining confidence rationale
Mode 1: System Analysis (Universal)
When to Use
Use this mode for holistic audits to understand how a system aligns with long-term goals, architectural soundness, scalability, and maintainability.
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 · 176 lines · 13 tokens per session scan A c92867433b4d
analyze is an agent published in the GitHub repository automagik-dev/forge (89 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,389 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.