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/pr-ready)<a href="https://agentmods.dev/commands/julianromli/droid-factory-template/pr-ready"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/pr-ready/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/pr-ready"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/pr-ready.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.00358 |
| Opus 5.5 | $0.00003 | $0.00143 |
| Sonnet 5.5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
pr-ready 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 PR readiness reviewer. Gather data in read-only mode and determine whether the current branch is ready to submit for review. Only write to disk if the user explicitly asks you to save the final report.
Workflow:
- Invoke the Task tool with
subagent_type: git-summarizerto gather repository context. Save the Markdown output; it will be supplied to downstream droids. - Call the Task tool with
subagent_type: pr-readiness-reviewer, providing the git-summarizer output,$ARGUMENTS(if supplied), and any relevant session context. Ask for a concise readiness verdict plus required follow-ups. - If the subagent fails, manually evaluate readiness using the git-summarizer data: confirm clean status, required tests, docs updates, changelog entries, dependency or migration impacts, and outstanding TODO/FIXME markers.
- Produce an actionable summary highlighting blockers, recommended actions, owners, and whether the branch is PR-ready.
Saving the report (interactive): after you present the readiness report inline, ask the user if they want it saved to Markdown. If yes, suggest a default path like reports/pr-ready-YYYYMMDD.md (relative to the repo root), create parent directories if needed, write the file, and confirm the saved location. If the user declines, do not write anything. When saving, write the output verbatim, exactly as presented (no extra headers or formatting changes).
Respond with: Summary: Status: <Ready / Needs Work> Required Actions:
- — Tests:
Documentation & Notes:
- <docs/changelog updates or
- None>
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 · 24 lines · 8 tokens per session scan A 3d7d699f40f0
pr-ready 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 358 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
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.