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/summary.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/summary.template)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/summary.template"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/summary.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.00611 |
| Opus 5 | $0.00000 | $0.00305 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
summary.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.
What it actually says
SUMMARY*[TASK_NAME]*[YYYYMMDD]
Overview
[2-3 sentence summary of what was attempted and current status - focus on what's broken or incomplete]
Outstanding Issues & Incomplete Work
Critical Issues
Issues that block functionality or prevent progress:
- 🔴 [Issue Title] (CRITICAL) - [Brief description]
- Impact: [What this breaks or prevents]
- Root Cause: [Why this happened]
- Resolution: [What needs to be done to fix it]
- Estimated Time: [Time needed to resolve]
Incomplete Tasks
Tasks from the plan that were not completed:
- 🔧 [Task Name] - [What was missed]
- Reason: [Why it wasn't completed]
- Impact: [What functionality is missing]
- Next Step: [What needs to happen]
Hidden TODOs & Technical Debt
Code TODOs and shortcuts discovered during review:
- 🧩 [File:line] - [TODO comment or technical shortcut]
- Impact: [What this affects]
- Refactoring Needed: [What should be done]
Discovered Problems
Issues found during implementation that weren't in the original plan:
- 🟡 [Problem Title] - [Description]
- Context: [How this was discovered]
- Priority: [HIGH/MEDIUM/LOW] - [Why this priority]
- Effort: [Time needed to address]
Brief Implementation Summary
What Was Implemented
- [Concise bullet point of major completion]
- [Another key deliverable that works]
Files Modified/Created
path/to/file.ext- [Brief description of changes]another/file.js- [What was added/modified]
Problems That Need Immediate Attention
- [Problem 1] - [Why this needs immediate focus]
- [Problem 2] - [Another urgent issue]
References
- Source Plan:
[path/to/plan.md] - Related Research:
[path/to/research.md](if applicable) - Modified Files: [List of key files changed]
Implementation Status: [🔴 BLOCKED | 🟡 PARTIAL | ✅ COMPLETE] - [One sentence status summary focused on what still needs work]
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 · 84 lines · 0 tokens per session scan A 8bfb7bf1aa5e
summary.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 611 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.