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/issue.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/issue.template)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/issue.template"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/issue.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.00374 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
issue.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
ISSUE_[NNN]_[BRIEF_DESCRIPTION]
Problem
[1-2 sentence description of what's broken or not working as expected]
Affected Components:
path/to/file.ext:line- [Brief description]another/file.js:line- [Brief description]
Impact
Severity: [Critical/High/Medium/Low] Why this matters: [Brief explanation of impact on functionality or users]
Solution
Recommended: Solution [1/2/3]
Solution 1: [Brief Solution Name] ⭐ (Recommended)
[Brief description of the recommended approach]
// Code example showing the fix
Why recommended: [1 sentence explaining why this is the best approach]
Solution 2: [Alternative Solution Name]
[Brief description of alternative approach]
Trade-offs: [1 sentence about pros/cons vs recommended solution]
Solution 3: [Another Alternative] (if applicable)
[Brief description of third option]
Trade-offs: [1 sentence about when this might be appropriate]
Verification
Quick Test:
# Command to verify the fix works
make test
Expected Result: [What should happen when the fix is working]
References
- Related Plan:
[path/to/plan.md](if applicable) - Source Files: [List of key files that need changes]
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 · 67 lines · 0 tokens per session scan A 278c1e7bcdf9
issue.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 374 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
project-recap
Generate a visual project recap for context switching.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
session-log
Create or append a session log entry.
my-tasks
Track, prioritize, and execute tasks with goal alignment and due date awareness. Claude doesn't just remind you — it helps get work done.