Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-basenpx agentmods add commands/fomo-driven-development/strategic-claude-base/create_issueWrote 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/create_issue)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/create_issue"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/create_issue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/create_issue"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/create_issue.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00009 | $0.01601 |
| Opus 5.5 | $0.00004 | $0.00640 |
| Sonnet 5.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 2mo 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.
- 2mo 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 11mo ago), licensed MIT. It adds 9 tokens to every session and 1,601 once invoked, about $0.0000 per session on Opus 5.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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
sync-linear
Sync current work with Linear ticket status.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.