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 commands/fomo-driven-development/strategic-claude-base/references.templategit clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWrote 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/commands/fomo-driven-development/strategic-claude-base/references.template)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/references.template"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/references.template.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.00000 | $0.01905 |
| Opus 5 | $0.00000 | $0.00953 |
| Sonnet 5 | $0.00000 | $0.00381 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
REFERENCES.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 4d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[Product/Project Name] References
Reference Implementation
The complete reference implementation directory is located at:
[/path/to/reference/implementation/]
Reference Directory Contents
- Complete Codebase: [Description of what the reference implementation contains]
- Architecture Patterns: [Key patterns and design approaches demonstrated]
- Implementation Examples: [Specific examples of how features are built]
- Documentation: [What documentation is available in the reference]
Local Repository Structure
Primary Repository
Location: [/path/to/main/repository/]
Key Directories:
[repository-name]/
├── [directory1]/ # [Purpose and contents]
│ ├── [subdirectory]/ # [Specific functionality]
│ └── [important-files] # [Key implementation files]
├── [directory2]/ # [Purpose and contents]
│ ├── [component-a]/ # [Component description]
│ └── [component-b]/ # [Component description]
├── [directory3]/ # [Purpose and contents]
└── [documentation]/ # [Documentation location]
Key Files to Reference:
[path/to/important/file.ext]- [What this file demonstrates or implements][path/to/pattern/example.ext]- [Pattern or approach shown here][path/to/config/file.conf]- [Configuration examples and best practices]
Supporting Repositories
[Secondary Repository Name]
Location: [/path/to/secondary/repository/]
Purpose: [Why this repository is relevant and what patterns it demonstrates]
Key Reference Points:
- [Specific pattern or implementation to study]
- [Configuration or setup approach to follow]
- [Testing strategy or structure to emulate]
[Tertiary Repository Name]
Location: [/path/to/tertiary/repository/]
Purpose: [Why this repository is relevant and what it provides]
Integration Examples:
- [How this integrates with the main system]
- [APIs or interfaces that are relevant]
- [Data models or schemas to reference]
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.
- 4d ago First seen · 304 lines · 0 tokens per session scan A bf29e5a856e0
REFERENCES.template is a command 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 1,905 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.