Borrowing it
Nothing to install: this file belongs to tlennon-ie/neurodock. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tlennon-ie/neurodock/main/.claude/agents/release-pilot.mdgit clone --depth 1 https://github.com/tlennon-ie/neurodockWrote 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/tlennon-ie/neurodock/release-pilot)<a href="https://agentmods.dev/agents/tlennon-ie/neurodock/release-pilot"><img src="https://agentmods.dev/badge/agents/tlennon-ie/neurodock/release-pilot.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.1 | $0.00064 | $0.01493 |
| Opus 5 | $0.00032 | $0.00746 |
| Sonnet 5 | $0.00013 | $0.00299 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
release-pilot 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 8d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 8d ago First seen · 128 lines · 64 tokens per session scan A 8c7cf1b5305d
release-pilot is an agent published in the GitHub repository tlennon-ie/neurodock (11 stars, last pushed 8d ago), licensed AGPL-3.0. It adds 64 tokens to every session and 1,493 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
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
release-engineer
Release engineering agent'i. Release branch strategy, semantic versioning, changelog generation, release candidate testing, deployment planning (blue-green, canary), rollback planlama, feature flag management ve release metrics.
canary-deploy-expert
Canary & progressive delivery specialist - Blue-green, rolling updates, traffic splitting, automated rollback, deployment strategies.
community-manager
Open source community yonetim agent'i. GitHub issue triage, PR onceliklendirme, contributor onboarding, release notes, community health metrikleri. vibecosystem ve diger acik kaynak projeler icin.
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
_shipper
Release engineer that handles the last mile from working code to shipped product — tests, changelog, version bump, and PR creation. Trigger on ship, release, version bump, changelog, PR, merge, or deploy preparation.