Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ribeirogab/specwright/plugin install swWrote 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/ribeirogab/specwright/delivery)<a href="https://agentmods.dev/commands/ribeirogab/specwright/delivery"><img src="https://agentmods.dev/badge/commands/ribeirogab/specwright/delivery/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/ribeirogab/specwright/delivery"><img src="https://agentmods.dev/badge/commands/ribeirogab/specwright/delivery.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.00038 | $0.00113 |
| Opus 5.5 | $0.00015 | $0.00045 |
| Sonnet 5.5 | $0.00008 | $0.00023 |
| Haiku 4.5 | $0.00004 | $0.00011 |
Grade A, and why
delivery 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.
What it actually says
delivery — conduct many changes to done
Run the specwright delivery skill. Read ${CLAUDE_PLUGIN_ROOT}/skills/delivery/SKILL.md and follow its instructions exactly, treating $ARGUMENTS as the skill's input.
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 · 9 lines · 38 tokens per session scan A 8bb35ec830e6
delivery is a command published in the GitHub repository ribeirogab/specwright (3 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 113 once invoked, about $0.0002 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
kiro-spec-tasks
Command "kiro-spec-tasks" from gotalab/cc-sdd, covering implementation tasks generator, core task, execution steps, step 1: load context and step 2: generate implementation tasks.
pulse-check
Pulse and worker utilisation diagnostics across repos.json, with self-improvement recommendations.
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).
speckit.companion.after-specify
Capture the current spec-kit step into .spec-context.json for the Companion GUI.
speckit.companion.before-step
Capture a spec-kit step's start into .spec-context.json for the Companion GUI.