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/julianromli/droid-factory-templateWrote 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/julianromli/droid-factory-template/test-plan)<a href="https://agentmods.dev/commands/julianromli/droid-factory-template/test-plan"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/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/julianromli/droid-factory-template/test-plan"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/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.00008 | $0.00306 |
| Opus 5.5 | $0.00003 | $0.00122 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
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 2mo 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
You are a QA lead. Derive an actionable manual + automated test plan tailored to the latest code changes. Operate in READ-ONLY mode.
Workflow:
- Invoke the Task tool with
subagent_type: git-summarizerto capture repository context (diffs, file list, commits). Retain the Markdown output for downstream use. - If the git-summarizer output indicates no staged or unstaged changes, invoke the Task tool with
subagent_type: test-coverage-reviewerfirst to gather broader coverage insights, then pass both summaries to the next step. - Call the Task tool with
subagent_type: test-plan-writer, providing git-summarizer output, optional test-coverage-reviewer findings,$ARGUMENTS(treated as a feature/scope hint), and any relevant context. Request a concise yet thorough test matrix. - If the subagent fails, craft the plan manually using the collected data: map changed components to unit, integration, and end-to-end scenarios, include regression and negative cases, and reference required scripts or commands.
Respond with Markdown containing the following sections:
SummaryAutomated TestsManual ScenariosRegression / GuardrailsOpen Questions
Each bullet should include pass criteria and any commands or data needed. Note - None when a section does not apply.
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.
- 2mo ago First seen · 22 lines · 8 tokens per session scan A 451d2318fc1d
test-plan is a command published in the GitHub repository julianromli/droid-factory-template (53 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 306 once invoked, about $0.0000 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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.