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/fomo-driven-development/strategic-claude-base/codebase-analyzer.templategit clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWhat 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.00000 | $0.00432 |
| Opus 5 | $0.00000 | $0.00216 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
codebase-analyzer.template 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.
What it actually says
Analysis: [Feature/Component Name]
Overview
[2-3 sentence summary of how it works]
Entry Points
cmd/root.go:25- Root command definitioncmd/process.go:18- ProcessFiles() command handler
Core Implementation
1. Input Validation (internal/validator/files.go:12-35)
- Validates file paths and permissions using filepath.Walk
- Checks file types against allowed extensions
- Returns error if validation fails
2. Data Processing (internal/processor/file_processor.go:45-89)
- Opens file handle at line 52
- Processes data in chunks using io.Reader at line 67
- Spawns goroutines for concurrent processing at line 78
3. State Management (internal/state/manager.go:23-67)
- Tracks processing state using channels
- Updates progress via sync.WaitGroup
- Implements graceful shutdown on SIGTERM
Data Flow
- Command parsed by cobra at
cmd/process.go:18 - Flags validated at
internal/validator/files.go:12 - Processing initiated at
internal/processor/file_processor.go:45 - Results collected at
internal/collector/results.go:34 - Output written to stdout/file at
cmd/process.go:89
Key Patterns
- Strategy Pattern: ProcessorStrategy interface at
internal/processor/strategy.go:8 - Worker Pool: Goroutine pool managed in
internal/worker/pool.go:15 - Context Cancellation: Context passed through call chain at
cmd/process.go:25
Configuration
- Config loaded via viper at
internal/config/config.go:15 - Environment variables parsed at
internal/config/config.go:28-45 - CLI flags defined at
cmd/root.go:45-62
Error Handling
- Input validation errors wrapped at
internal/validator/files.go:28 - Processing errors collected in error channel (
internal/processor/file_processor.go:82) - Failed operations logged via logrus to stderr
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 · 57 lines · 0 tokens per session scan A 7314ea287e36
codebase-analyzer.template is an agent published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 432 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.