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/johnreitano/spekka/implement-tasksgit clone --depth 1 https://github.com/johnreitano/spekkaWhat 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.00000 | $0.00784 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
implement-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 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Implementation Process
Now that we have a spec and tasks list ready for implementation, we will proceed with implementation of this spec by following this multi-phase process:
PHASE 1: Determine which task group(s) from tasks.md should be implemented PHASE 2: Delegate implementation to the implementer subagent PHASE 3: After ALL task groups have been implemented, delegate to implementation-verifier to produce the final verification report.
Follow each of these phases and their individual workflows IN SEQUENCE:
Multi-Phase Process
PHASE 1: Determine which task group(s) to implement
First, check if the user has already provided instructions about which task group(s) to implement.
If the user HAS provided instructions: Proceed to PHASE 2 to delegate implementation of those specified task group(s) to the implementer subagent.
If the user has NOT provided instructions:
Read spekka/specs/[this-spec]/tasks.md to review the available task groups, then output the following message to the user and WAIT for their response:
Should we proceed with implementation of all task groups in tasks.md?
If not, then please specify which task(s) to implement.
PHASE 2: Delegate implementation to the implementer subagent
Delegate to the implementer subagent to implement the specified task group(s):
Provide to the subagent:
- The specific task group(s) from
spekka/specs/[this-spec]/tasks.mdincluding the parent task, all sub-tasks, and any sub-bullet points - The path to this spec's documentation:
spekka/specs/[this-spec]/spec.md - The path to this spec's requirements:
spekka/specs/[this-spec]/planning/requirements.md - The path to this spec's visuals (if any):
spekka/specs/[this-spec]/planning/visuals
Instruct the subagent to:
- Analyze the provided spec.md, requirements.md, and visuals (if any)
- Analyze patterns in the codebase according to its built-in workflow
- IF your task involves user-facing UI, and IF any of the views and UI elements that you will be modifying already exist, and IF you have access to a browser testing tool (such as the Playwright MCP server), THEN
- Using this browser testing tool, use all of these pre-existing views and/or UI elements as if you are a user to capture their visual appearance BEFORE your change.
- Take before-change screenshots of these views and UI elements you will be modifying and store those in
spekka/specs/[this-spec]/verification/screenshots/before-change/. Do not store before-change screenshots anywhere in the codebase other than this location.
- Implement the assigned task group according to requirements
- Update
spekka/specs/[this-spec]/tasks.mdto update the tasks you've implemented to mark that as done by updating their checkbox to checked state:- [x]
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 · 59 lines · 0 tokens per session scan A b3fc5fcd26b8
implement-tasks is a command published in the GitHub repository johnreitano/spekka (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 784 tokens. 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.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).