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.tasksgit 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.00018 | $0.01538 |
| Opus 5 | $0.00009 | $0.00769 |
| Sonnet 5 | $0.00004 | $0.00308 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
speckit.tasks 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.
This is a copy
94% identical to speckit.tasks — 4 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 — 140 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).
Outline
-
Setup: Run
.specify/scripts/bash/check-prerequisites.sh --jsonfrom 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"). -
Load design documents: Read from FEATURE_DIR:
- Required: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
- Optional: data-model.md (entities), contracts/ (API endpoints), research.md (decisions), quickstart.md (test scenarios)
- Note: Not all projects have all documents. Generate tasks based on what's available.
-
Execute task generation workflow:
- Load plan.md and extract tech stack, libraries, project structure
- Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
- If data-model.md exists: Extract entities and map to user stories
- If contracts/ exists: Map endpoints to user stories
- If research.md exists: Extract decisions for setup tasks
- Generate tasks organized by user story (see Task Generation Rules below)
- Generate dependency graph showing user story completion order
- Create parallel execution examples per user story
- Validate task completeness (each user story has all needed tasks, independently testable)
-
Generate tasks.md: Use
.specify.specify/templates/tasks-template.mdas structure, fill with:- Correct feature name from plan.md
- Phase 1: Setup tasks (project initialization)
- Phase 2: Foundational tasks (blocking prerequisites for all user stories)
- Phase 3+: One phase per user story (in priority order from spec.md)
- Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
- Final Phase: Polish & cross-cutting concerns
- All tasks must follow the strict checklist format (see Task Generation Rules below)
- Clear file paths for each task
- Dependencies section showing story completion order
- Parallel execution examples per story
- Implementation strategy section (MVP first, incremental delivery)
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 · 140 lines · 18 tokens per session scan A 522b316a7295
speckit.tasks is a command published in the GitHub repository rshade/finfocus (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,538 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to speckit.tasks, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
pr-review
Review a pull request — gather metadata, diff, and existing feedback, then give a verdict.
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.
coaching-conversation-patterns
AI coaching and conversational support — empathetic interactions, safety guardrails, motivational interviewing, SMART goals, and crisis handling for coaching, therapy, education, or customer support. Use when building a coaching or support conversation, adding safety guardrails, or handling sensitive user disclosures.…
langfuse-observability
LLM observability with self-hosted Langfuse — tracing, evaluation, prompt versioning, cost tracking, and LLM-as-judge scoring. Use when adding LLM tracing, monitoring token cost, versioning prompts, or building evaluation dashboards. Triggers on Langfuse, LLM observability, tracing, prompt versioning, cost tracking…
streaming-api-patterns
Real-time data streaming with SSE, WebSockets, and ReadableStream. Use when implementing token streaming, Server-Sent Events, backpressure handling, or reconnection strategies. Triggers on streaming, SSE, Server-Sent Events, WebSocket, ReadableStream, backpressure, reconnection, token streaming.