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/rshade/finfocus/speckit.implementgit clone --depth 1 https://github.com/rshade/finfocusWhat 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.00014 | $0.02627 |
| Opus 5 | $0.00007 | $0.01314 |
| Sonnet 5 | $0.00003 | $0.00525 |
| Haiku 4.5 | $0.00001 | $0.00263 |
Grade A, and why
speckit.implement 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 2d 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.
This is a copy
81% identical to speckit.implement — 74 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Batch Processing (Context Window Optimization)
To maintain code quality and reduce CodeRabbit/review issues, this skill processes tasks in batches to prevent context window bloat from degrading output quality.
Default batch size: 5 tasks per invocation.
Override: User can pass --batch N in arguments (e.g., /speckit.implement --batch 3).
Behavior:
-
After parsing tasks.md, count pending tasks (not marked
[X]or[x]) -
If pending tasks exceed the batch size, only process the first N pending tasks
-
After completing the batch, STOP and output:
--- BATCH COMPLETE --- Processed: [N] tasks ([list task IDs]) Remaining: [M] tasks pending To continue: Run /clear then /speckit.implement This sheds accumulated context and improves code quality for remaining tasks. --- -
Do NOT continue processing beyond the batch limit
-
Mark completed tasks as
[X]in tasks.md before stopping so the next invocation picks up where you left off
Outline
-
Run
.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasksfrom repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). -
Check checklists status (if FEATURE_DIR/checklists/ exists):
-
Scan all checklist files in the checklists/ directory
-
For each checklist, count:
- Total items: All lines matching
- [ ]or- [X]or- [x] - Completed items: Lines matching
- [X]or- [x] - Incomplete items: Lines matching
- [ ]
- Total items: All lines matching
-
Create a status table:
| Checklist | Total | Completed | Incomplete | Status | |-----------|-------|-----------|------------|--------| | ux.md | 12 | 12 | 0 | ✓ PASS | | test.md | 8 | 5 | 3 | ✗ FAIL | | security.md | 6 | 6 | 0 | ✓ PASS |
-
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.
- 2d ago First seen · 185 lines · 14 tokens per session scan A 3d8050aae7ae
speckit.implement is a command published in the GitHub repository rshade/finfocus (5 stars, last pushed 16d ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,627 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to speckit.implement, differing in 74 lines, and is treated as a copy.
Other commands, from other repositories
release-notes
Draft curated release notes for a milestone release.
create-issue
Create a GitHub issue from the repo's templates, with the right type and labels.
review-code
Review a GitHub pull request for the OpenOps codebase. Checks out the PR, analyzes changes through OpenOps-specific lenses, validates findings with confidence scoring, previews before posting, and supports inline comments.
soc2-review
Assess SOC 2 readiness against the Trust Services Criteria and produce a readiness dashboard.
scan
Scan AWS account for cost optimization.
costguard-audit
Audit registered workspaces for CI-minute and cron waste, plus read-only cloud provider billing checks. Quantifies estimated monthly waste and prints a Markdown (or JSON) report.