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/koolamusic/claudefiles/plangit clone --depth 1 https://github.com/koolamusic/claudefilesWhat 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.00048 | $0.01259 |
| Opus 5 | $0.00024 | $0.00629 |
| Sonnet 5 | $0.00010 | $0.00252 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
plan 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convert the active sprint's RESEARCH.md into one or more executable PLAN files (one per wave-plan), plus CONTEXT.md.
Parse the input
$ARGUMENTS may include --push-issue. No other flags.
Steps
-
Locate the active sprint:
slug=$(cat .jira/CURRENT). If empty or missing, stop — there's no active sprint to plan. -
Verify inputs exist:
.jira/sprints/<slug>/BRIEF.md.jira/sprints/<slug>/RESEARCH.md
If either missing, stop and tell the user to run
/jira:researchfirst. -
First pass — spawn
jira-planner:- Sprint slug
- Brief path, research path
- Context path:
.jira/sprints/<slug>/CONTEXT.md(may not exist; planner creates it) - Plan output dir:
.jira/sprints/<slug>/ - References: PLAN template + CONTEXT template + feature template (
templates/sprint/feature.feature)
The planner writes
features/*.feature(the sprint's acceptance predicates,@req:<ID>tagged) before the plans; plans claim predicates viaeffects:frontmatter.The planner may use
AskUserQuestion(≤ 4 questions, bundled) for load-bearing ambiguity. Answers become CONTEXT.md decisions (D-XX). -
Handle planner return. One of:
## PLANNING COMPLETE— proceed to step 5.## ⚠ Source Audit: Unplanned Items Found— surface the gap list viaAskUserQuestion. Three options: A) re-spawn planner with instruction to add covering plans, B) split sprint, C) defer items to CONTEXT.md## Deferred ideas. Then proceed.## SPRINT SPLIT RECOMMENDED— surface the proposal viaAskUserQuestion. If user accepts, create the sub-sprint dirs and re-route to research. If user proceeds anyway, re-spawn planner with "force-fit" instruction.
-
Audit pass — spawn
jira-plan-checkerwith all*-PLAN.mdpaths +features/*.featurepaths + brief + research + context. Returns a YAML block withverdict,issue_count,findings,required_revisions. -
Stall-aware revision loop (max 2 iterations):
- Track
prev_issue_count(initialized to ∞ before the first audit). - If
verdict: REVISE:- If
issue_count >= prev_issue_count: stalled — surface findings viaAskUserQuestionwith options: A) proceed-with-issues, B) re-spawn planner with explicit guidance, C) abandon. Exit if A or C. - Otherwise: re-spawn
jira-plannerwithrequired_revisionsappended. Re-audit. Setprev_issue_count = issue_count. - At most 2 iterations. After the second audit if still REVISE: surface findings, ask the user to accept-as-is / manually-edit / abandon.
- If
- Track
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 · 89 lines · 48 tokens per session scan A 5197fa219bb0
plan is a command published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,259 once invoked, about $0.0002 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-30.
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.