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.
git clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/ronronner02/codepilot-agent/spec-write-tasks)<a href="https://agentmods.dev/commands/ronronner02/codepilot-agent/spec-write-tasks"><img src="https://agentmods.dev/badge/commands/ronronner02/codepilot-agent/spec-write-tasks/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/ronronner02/codepilot-agent/spec-write-tasks"><img src="https://agentmods.dev/badge/commands/ronronner02/codepilot-agent/spec-write-tasks.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.00110 | $0.02247 |
| Opus 5.5 | $0.00044 | $0.00899 |
| Sonnet 5.5 | $0.00022 | $0.00449 |
| Haiku 4.5 | $0.00011 | $0.00225 |
Grade A, and why
spec-write-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 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command support root: .claude/spec-first/workflows/spec-write-tasks. Treat it as the loaded skill directory whenever this inlined workflow refers to SKILL_DIR or the directory containing SKILL.md.
spec-write-tasks
spec-write-tasks is an optional derived layer between spec-plan and spec-work. It does not execute code. It either compiles a settled source plan into a derived task pack, validates an existing task pack, or returns a no-task-pack decision.
It is a public workflow with the unified entrypoint spec-write-tasks.
Purpose
Decide whether a derived task pack is worthwhile, compile one when it reduces execution risk or context load, and validate existing task packs before they reach spec-work.
Workflow Contract Summary
When To Use
Use when a settled local source plan is too large or dependent for direct execution, when the user explicitly asks to split a plan into tasks, or when an existing local task pack needs validation before spec-work.
When Not To Use
Do not use for unresolved product or architecture scope, small changes that do not need a derived layer, remote repositories or package names, marketplace skill lookup, or implementation prompts that should go directly to spec-work.
Inputs
A local source plan path, existing task-pack path, or clear task-splitting request that resolves to one local source plan. Inputs must stay local and source-owned; remote repos, packages, marketplace identifiers, and generic task lists are rejected.
Outputs
One of: executable derived task pack, validated existing task-pack handoff, skip, return-to-plan, draft-only, or validate-only envelope. Task packs are derived execution indexes and never replace the source plan.
Artifacts
Executable task packs live under docs/tasks/ and must carry an artifact-root-relative POSIX source_plan, canonical source_plan_hash, generated_by: spec-write-tasks, mode: derived, and a valid Task Pack Contract JSON block. Executable identity is source-plan-path+body-hash; spec_id is an optional compatibility trace rather than a required identity field.
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 · 141 lines · 110 tokens per session scan A 83152263b63f
spec-write-tasks is a command published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 2,247 once invoked, about $0.0004 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-31.
Other commands, from other repositories
PyTest.GateKeeper
You are a Senior QA Automation Engineer with deep expertise in Python testing and the pytest framework.
acos
The single command you need. ACOS auto-routes everything.
acos-checkpoint
Create checkpoints before risky operations. Rollback if things go wrong.
attune
AI-powered developer workflows with Socratic discovery.
push
This command will push new design file into the given jira ticket With this command the user will provide arguments.
agent
Create and manage custom AI agents.