Borrowing it
Nothing to install: this file belongs to rshade/finfocus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rshade/finfocus/main/.claude/commands/speckit.implement.mdgit clone --depth 1 https://github.com/rshade/finfocusWrote 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/rshade/finfocus/speckit.implement)<a href="https://agentmods.dev/commands/rshade/finfocus/speckit.implement"><img src="https://agentmods.dev/badge/commands/rshade/finfocus/speckit.implement/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/rshade/finfocus/speckit.implement"><img src="https://agentmods.dev/badge/commands/rshade/finfocus/speckit.implement.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.00014 | $0.02627 |
| Opus 5.5 | $0.00006 | $0.01051 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 185 lines · 14 tokens per session scan A 3d8050aae7ae
speckit.implement is a command published in the GitHub repository rshade/finfocus (10 stars, last pushed 2d 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.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
scan
Scan AWS account for cost optimization.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.
ollama-local
Local LLM inference with Ollama. Use when setting up local models for development, running models in CI pipelines, or reducing inference cost. Triggers on Ollama, local LLM, local inference, offline model, self-hosted model, LangChain Ollama, model quantization.
archive-ledger
../../../shared/commands/archive-ledger.md.
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.