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 skills add lindoelio/spec-driven-steroids --skill spec-driven-task-implementergit clone --depth 1 https://github.com/lindoelio/spec-driven-steroidsWrote 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/skills/lindoelio/spec-driven-steroids/spec-driven-task-implementer)<a href="https://agentmods.dev/skills/lindoelio/spec-driven-steroids/spec-driven-task-implementer"><img src="https://agentmods.dev/badge/skills/lindoelio/spec-driven-steroids/spec-driven-task-implementer/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/skills/lindoelio/spec-driven-steroids/spec-driven-task-implementer"><img src="https://agentmods.dev/badge/skills/lindoelio/spec-driven-steroids/spec-driven-task-implementer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 251 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00070 | $0.02775 |
| Opus 5.5 | $0.00028 | $0.01110 |
| Sonnet 5.5 | $0.00014 | $0.00555 |
| Haiku 4.5 | $0.00007 | $0.00278 |
Grade A, and why
spec-driven-task-implementer 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 today.
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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Task Implementer Skill
Implement approved spec-driven work by executing tasks from tasks.md in a disciplined, traceable loop.
Your job is to:
- implement only what the spec and task plan require
- keep changes small, scoped, and consistent with the repository
- update task status in
tasks.mdas work progresses - verify each task before marking it complete
- preserve the traceability chain from implementation back to
DES-*andREQ-*
Default path: validate the complete spec and confirm human implementation approval, resolve the approved execution scope below, then implement and verify eligible tasks in dependency order. Never infer permission to implement from file existence or from another agent's recommendation.
Read references/task-execution-patterns.md when you need examples for resuming interrupted work, choosing the smallest meaningful verification, or handling failed verification loops.
Read references/parallel-execution-patterns.md when executing a phase or full feature on a platform that supports sub-agent parallelism (e.g., OpenCode).
Shared Protocol
Follow the Context Preflight and Phase Gate protocols in the spec-driven-shared-protocol skill's references/shared-protocol.md.
Per-Phase Todo List
When this skill begins execution, create a todo list derived from the pending tasks in the approved tasks.md for the target slug. Each pending task becomes a todo item. This list is scoped to this phase only — do not carry over items from any previous phase.
Item Derivation
- Read the approved
tasks.mdfor the target slug. - For each task that is
- [ ](pending), create a corresponding todo item. - Skip completed tasks; recover any in-progress task under Interrupted Sessions before selecting new work.
Progress Rules
- Mark an item
in_progresswhen starting that task. - Mark an item
completedonly after the task has been verified and marked- [x]intasks.md. - Do not mark an item
completeduntil verification passes. - Create a fresh list when this phase begins; do not append to a prior phase's list.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +4 lines 864e8a402c3c
- 1mo ago First seen · 255 lines · 70 tokens per session scan A 909d0245cda2
spec-driven-task-implementer is a skill published in the GitHub repository lindoelio/spec-driven-steroids (54 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 2,775 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
evidence-led-authoring
Shared bootstrap-owner contract for evidence-backed brownfield candidates, provenance, and imported baseline coverage.
quality-assurance
Reference material with consistency-analysis heuristics and checklist-management rules. Loaded on demand by analyze-compliance and quality-control; not directly invokable.
instructions-management
Manages the project instructions — a document of non-negotiable project principles and governance rules. Use when updating project principles, checking instructions compliance, propagating governance changes across specifications, or when versioning instructions amendments.
sddp-amend
Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only; do not select for general queries.
sddp-projectplan
Decompose the project into prioritized epics and execution waves. Direct command-bar dispatch only; do not select for general queries.