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/juliusz-cwiakalski/agentic-delivery-osWrote 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/juliusz-cwiakalski/agentic-delivery-os/write-test-plan)<a href="https://agentmods.dev/commands/juliusz-cwiakalski/agentic-delivery-os/write-test-plan"><img src="https://agentmods.dev/badge/commands/juliusz-cwiakalski/agentic-delivery-os/write-test-plan/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/juliusz-cwiakalski/agentic-delivery-os/write-test-plan"><img src="https://agentmods.dev/badge/commands/juliusz-cwiakalski/agentic-delivery-os/write-test-plan.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.00006 | $0.00814 |
| Opus 5 | $0.00003 | $0.00407 |
| Sonnet 5 | $0.00001 | $0.00163 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
write-test-plan 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.
What it actually says
User invocation: /write-test-plan <workItemRef> [options]
Options: focus=backend, nfr-only, no-manual, etc.
The TEST PLAN:
- Ensures full coverage of capabilities, interfaces, and acceptance criteria
- Aligns with implementation plan phases
- Maps scenarios to test types per
.ai/rules/testing-strategy.md
<discovery_rules>
Given workItemRef:
- Search for folder:
doc/changes/**/*--<workItemRef>--*/ - Locate spec:
chg-<workItemRef>-spec.md(required) - Locate plan:
chg-<workItemRef>-plan.md(optional) - Read:
.ai/rules/testing-strategy.md(required)
Files:
- Spec:
chg-<workItemRef>-spec.md - Plan:
chg-<workItemRef>-plan.md - Test Plan:
chg-<workItemRef>-test-plan.md - Branch:
<change.type>/<workItemRef>/<slug></discovery_rules>
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 · 83 lines · 6 tokens per session scan A a456de744f0e
write-test-plan is a command published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (37 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 814 once invoked, about $0.0000 per session on Opus 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-09-07.
Other commands, from other repositories
distill
Creates E2E acceptance tests in Given-When-Then format from requirements and architecture. Use when preparing executable specifications before implementation.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…
test-management
Organize, classify, and trace Katalon True Platform/TestOps test assets. Use when you need to structure test cases into folders and suites, move or reorganize cases, search and find existing assets at scale, link or unlink requirements to test cases, or produce a requirement-to-test traceability report (which…
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…