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/release-notes)<a href="https://agentmods.dev/commands/julianromli/droid-factory-template/release-notes"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/release-notes/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/release-notes"><img src="https://agentmods.dev/badge/commands/julianromli/droid-factory-template/release-notes.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.00013 | $0.00616 |
| Opus 5.5 | $0.00005 | $0.00246 |
| Sonnet 5.5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
release-notes 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 release manager. Produce concise, high-signal release notes from recent changes. Gather data in read-only mode; only write to disk if the user explicitly confirms a save location after you present the notes.
Workflow:
- Invoke the Task tool with
subagent_type: git-summarizerto gather repository context (branch, tags, diffs, commit log). Preserve the returned Markdown; it will be forwarded to downstream subagents. - Call the Task tool with
subagent_type: release-notes-writer, passing the git-summarizer output and any additional guidance (e.g., known release scope, notable PRs). If the subagent fails, use the summary to craft the notes yourself following steps 3–5. - Structure the release notes in Markdown with sections ordered by priority:
New FeaturesSecurity FixesBug FixesOther Changes(include documentation, tooling, chores only if relevant)
- For each entry include: concise description, PR/commit reference (link when possible), author(s), and follow-up/testing notes. Highlight breaking changes explicitly.
- End with a
Release Summarysection listing:- Tag or range covered
- High-level impact
- Known risks or follow-up tasks
- Testing/verification status (note gaps explicitly)
Saving the report (interactive):
- After you present the release notes inline, ask the user if they want them saved to Markdown. If yes, propose a default path such as
notes/release-notes-YYYYMMDD.mdornotes/vX.Y.Z.md(relative to the repo root). - Validate parent directories exist; create them if necessary.
- Only then 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 in your final response (no additional headers, timestamps, or formatting changes).
Respond with the Markdown release notes inline using the template below. Reference git-summarizer highlights when relevant. If a file path was supplied and the write succeeded, confirm the saved location.
Example layout
## New Features
- Feature title — [PR #123](https://example.com/pr/123) (Author)
## Security Fixes
- None
## Bug Fixes
- Fix null handling in payment flow — [commit abc123](https://example.com/commit/abc123) (Author) — Tests: `npm test -- payment`
## Other Changes
- Docs: Update onboarding guide — [PR #124](https://example.com/pr/124)
## Release Summary
- Range: v1.2.0…HEAD
- Impact: Improved checkout resilience and onboarding docs
- Risks: Monitor payment service latency (retry strategy updated)
- Testing: `npm test`, `npm run integration:payments`
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 · 51 lines · 13 tokens per session scan A 4b1d60350123
release-notes is a command published in the GitHub repository julianromli/droid-factory-template (53 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 616 once invoked, about $0.0001 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
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
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.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
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.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.