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.
npx agentmods add commands/rhyanvargas/agentic-development-starter-kit/setup-releasesgit clone --depth 1 https://github.com/rhyanvargas/agentic-development-starter-kitWrote 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/rhyanvargas/agentic-development-starter-kit/setup-releases)<a href="https://agentmods.dev/commands/rhyanvargas/agentic-development-starter-kit/setup-releases"><img src="https://agentmods.dev/badge/commands/rhyanvargas/agentic-development-starter-kit/setup-releases.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00180 |
| Opus 5 | $0.00000 | $0.00090 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
setup-releases 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 4d 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
/setup-releases
Wire Conventional Commits–based version and changelog automation for this repo.
Skill
Read and follow skills/release-automation (adopter apps: .agents/skills/release-automation).
Usage
/setup-releases
/setup-releases "Azure DevOps + squash merge on main"
/setup-releases "GitHub Actions + release-please, start at 0.1.0"
Behavior
- Confirm DevOps platform from evidence + user (GitHub Actions, Azure DevOps, or other).
- Persist the choice in the skill’s
references/project-context.md. - Install matching automation; update
docs/RELEASE.mdand Conventional Commit PR guidance. - Call out any manual org settings (e.g. Actions allowed to open PRs, Azure tag permissions).
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.
- 4d ago First seen · 23 lines · 0 tokens per session scan A 1a8697626b39
setup-releases is a command published in the GitHub repository rhyanvargas/agentic-development-starter-kit (2 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 180 tokens. 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
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
ship
Deliver the increment. Then go live with a rollback you have run.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
release-tag
Create and push a version tag after a release PR has been merged.
release
Orchestrate a complete release workflow with quality gates, version bumping, and publishing automation.