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/neuromechanist/research-skillsWrote 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/agents/neuromechanist/research-skills/release-prep)<a href="https://agentmods.dev/agents/neuromechanist/research-skills/release-prep"><img src="https://agentmods.dev/badge/agents/neuromechanist/research-skills/release-prep/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/agents/neuromechanist/research-skills/release-prep"><img src="https://agentmods.dev/badge/agents/neuromechanist/research-skills/release-prep.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.00055 | $0.00542 |
| Opus 5 | $0.00028 | $0.00271 |
| Sonnet 5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
release-prep 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 10d 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
Release Preparation Agent
Autonomously validate that a project is ready for release by running a comprehensive checklist.
Procedure
1. Identify Version and Project Type
Read version from config files (pyproject.toml, package.json, Cargo.toml). Identify the project stack. If no version is found, report an error.
2. Run Pre-release Checklist
Tests
# Python
uv run pytest --tb=short; echo "TEST_EXIT=$?"
# JavaScript
bun test; echo "TEST_EXIT=$?"
Check the exit code to determine pass/fail status.
Lint
# Python
uv run ruff check .; echo "LINT_EXIT=$?"
# JavaScript
bunx biome check .; echo "LINT_EXIT=$?"
Coverage
# Python
uv run pytest --cov --cov-report=term-missing
Uncommitted Changes
git status --short
git diff --stat
CI Status
gh run list --limit 5 || echo "WARNING: Could not check CI status"
Changelog/Release Notes
Check if CHANGELOG.md exists and has an entry for the upcoming version.
License
Check LICENSE file exists.
Security blockers
If a security-audit or dependency-auditor report exists for this release cycle, any Critical finding in it is a release blocker: list it in the Blockers section and report "Ready to Release: NO" until it is resolved.
3. Generate Report
## Release Readiness Report
Version: X.Y.Z
Branch: main
Last CI run: passing/failing
### Checklist
- [x] All tests passing (N tests)
- [x] Lint clean
- [x] Coverage: XX%
- [ ] CHANGELOG.md updated for vX.Y.Z
- [x] No uncommitted changes
- [x] CI green on latest commit
- [x] LICENSE file present
### Blockers
1. CHANGELOG.md missing entry for vX.Y.Z
### Ready to Release: NO (1 blocker)
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.
- 10d ago First seen · 92 lines · 55 tokens per session scan A c47f3103b07e
release-prep is an agent published in the GitHub repository neuromechanist/research-skills (45 stars, last pushed 7d ago), licensed BSD-3-Clause. It adds 55 tokens to every session and 542 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
pm-changelog-curator
Drafts CHANGELOG entries from git log applying pm-skills CHANGELOG hygiene rules from CLAUDE.md: describe what changed (not where), public paths only, never reference gitignored NOTES/ or agent-context/SESSION-LOG/ or docs/internal/efforts/. Distinguishes user-facing from internal-only commits. Returns a draft for…
pm-release-conductor
Guided release runbook with 6 explicit gates (G0 Pre-tag readiness, G1 Adversarial review, G2 Version bump + CHANGELOG prep, G2.5 Commit release-prep + re-verify, G3 Tag + push, G4 Post-tag hygiene). Chains to pm-skill-auditor at G0 (and again at G2.5 verification) and to pm-changelog-curator at G2. Refuses to advance…
godot-tools-engineer
Use this agent for Godot 4.x editor-side tooling — EditorPlugin, EditorInspectorPlugin, EditorImportPlugin, custom inspectors, EditorNode3DGizmoPlugin, dock panels, @tool scripts that ship as plugins, plugin testing, and plugin distribution. Works in both GDScript and C# (with #if TOOLS guards). GDExtension (C++…
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
godmode-shipping
Release Gatekeeper, QA & Verification Auditor. Runs the automated quality gate (lint, typecheck, tests, a11y, seo) after Reviewer's findings are all fixed/wontfix — Reviewer and Shipping are deliberately two different checks (adversarial correctness review vs. mechanical gate execution), not one merged step. Ensures…
changelog-manager
Manages changelog generation and version tracking. Use after commits, before releases, or when preparing release notes. Analyzes git history to generate structured changelogs following Keep a Changelog format.