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/create_issuegit 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.00009 | $0.01601 |
| Opus 5 | $0.00005 | $0.00800 |
| Sonnet 5 | $0.00002 | $0.00320 |
| Haiku 4.5 | $0.00001 | $0.00160 |
Grade A, and why
create_issue 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 3d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are tasked with creating brief, solution-focused issue documentation for problems discovered during development work. You should be fast, focused, and avoid extensive research - document what you know from context.
Subject/File provided: $1
Initial Response
When this command is invoked:
-
Check if subject/file was provided:
- If subject/file was provided as parameter, proceed with analysis
- If no subject provided, respond with:
I'll help you create an issue document for a problem you've discovered. Please provide: 1. A brief description of the issue, or 2. A summary file path to extract issues from Examples: - `/create_issue authentication failing in production` - `/create_issue @.strategic-claude-basic/summary/SUMMARY_0001_07-09-2025_sat_user-auth.md` I'll document the issue quickly without extensive solution research.Then wait for the user's input.
Process Steps
Step 1: Input Analysis
-
Determine input type:
If it's a file path (starts with @. or contains .md):
- Read the specified file completely
- Look for sections about problems, issues, or incomplete work
- Prepare to create multiple issues if needed
If it's a description:
- Use the provided subject as the issue description
- Look at conversation context for additional details
- Prepare to create a single issue
-
Present scope:
For file input:
Reading summary file: [filename] Found [N] issues to document: - [Brief issue 1] - [Brief issue 2] - [Brief issue 3] I'll create individual issue documents for each problem found. Proceeding with issue creation...For subject input:
Creating issue documentation for: [subject] I'll document this issue based on the current context and any known details. Proceeding with issue creation...
Step 2: Issue Extraction and Analysis
CRITICAL: Do NOT spawn research agents or extensive analysis. Only use information already available.
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.
- 3d ago First seen · 246 lines · 9 tokens per session scan A 17f36bf8e5fb
create_issue is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 1,601 once invoked, about $0.0000 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-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.