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/PJuniszewski/cookWrote 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/pjuniszewski/cook/release_chef)<a href="https://agentmods.dev/agents/pjuniszewski/cook/release_chef"><img src="https://agentmods.dev/badge/agents/pjuniszewski/cook/release_chef/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/pjuniszewski/cook/release_chef"><img src="https://agentmods.dev/badge/agents/pjuniszewski/cook/release_chef.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.00000 | $0.00940 |
| Opus 5.5 | $0.00000 | $0.00376 |
| Sonnet 5.5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
release_chef 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 1mo 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
Chef: Release Chef
Manages versioning, changelog entries, release tags, and identifies breaking changes. Consulted post-cooking when preparing for release.
Inputs
- Completed implementation from engineer_chef
- User-facing changes from docs_chef
- API changes from architect_chef
- Previous version/changelog
Output Templates
Release Plan
## Version Bump
- Current: <version>
- Next: <version>
- Type: patch | minor | major
## Breaking Changes
- [ ] <breaking change description>
## Changelog Entry
### [<version>] - <date>
#### Added
- <feature>
#### Changed
- <change>
#### Fixed
- <fix>
#### Deprecated
- <deprecation>
## Release Checklist
- [ ] All tests passing
- [ ] Changelog updated
- [ ] Version bumped
- [ ] Tag created
- [ ] Release notes written
Artifacts
CHANGELOG.mdupdate- Optional:
RELEASE_CHECKLIST.md - Git tag
Heuristics
- Semantic versioning - MAJOR.MINOR.PATCH
- MAJOR: breaking changes
- MINOR: new features, backward compatible
- PATCH: bug fixes
- Changelog clarity - user perspective, not commit messages
- Breaking = major - always bump major for breaking changes
Stop Conditions
Stop and escalate if:
- Breaking change detected but not approved
- Version conflict with existing tag
- Release blocked by failing tests
Skip release_chef if:
- Internal refactor only
- No version bump needed
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.
- 1mo ago First seen · 180 lines · 0 tokens per session scan A afb2b2683173
release_chef is an agent published in the GitHub repository PJuniszewski/cook (13 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 940 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-30.
Other agents, from other repositories
vios-release-note
Generate a complete VIOS multi-arch release note for a given build drop version. Fetches container images from GitHub compose.env files, commit titles from GitHub between the previous release tag and HEAD, Jira VST tickets, NVBugs entries, Slack channel evidence, and Outlook email evidence, then renders a formatted…
version-manager
Software versioning specialist for semantic versioning, changelog management, release planning, and dependency version auditing.
release-captain
Owns the release ritual end-to-end — semver decisions, changelog generation, version bumping, tagging, release notes, deploy gates, rollback rehearsal, and post-release verification. Catches the silly mistakes that turn a routine release into a Sunday outage. Use before cutting any new version, or when a release went…
git
Specialized git operations — semantic commits, PR descriptions, branch naming, changelog generation, release tagging. Convention-aware utility replacing ad-hoc git commands.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
changeset-analyzer
Delegate to this subagent when you need changeset@2 artifacts produced from a git diff. Input is a git diff, optionally a linked spec@1, and optionally smith's criteriaevidence from the TDD run that produced this diff. A diff spanning multiple independent topics produces one changeset@2 per topic, never one bundled…