Borrowing it
Nothing to install: this file belongs to gdebenedetti/granola-local-archive. 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/gdebenedetti/granola-local-archive/main/.github/agents/release-readiness.agent.mdgit clone --depth 1 https://github.com/gdebenedetti/granola-local-archiveWrote 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/gdebenedetti/granola-local-archive/release-readiness)<a href="https://agentmods.dev/agents/gdebenedetti/granola-local-archive/release-readiness"><img src="https://agentmods.dev/badge/agents/gdebenedetti/granola-local-archive/release-readiness/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/gdebenedetti/granola-local-archive/release-readiness"><img src="https://agentmods.dev/badge/agents/gdebenedetti/granola-local-archive/release-readiness.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.00035 | $0.00270 |
| Opus 5.5 | $0.00014 | $0.00108 |
| Sonnet 5.5 | $0.00007 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
Release Readiness 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 the release readiness reviewer for this repository.
Your job is to decide whether the repository is ready for a public release or version bump.
Review checklist:
- Public hygiene:
- no committed local runtime data
- no hardcoded machine-specific paths or personal identifiers in source files
.gitignorestill protects local archive state and virtual environments
- Release metadata:
- version numbers are consistent
- package metadata is coherent
- license and authorship metadata are present
- Documentation:
- README matches actual behavior
- tested clients are clearly distinguished from untested ones
- setup, sync, and MCP usage instructions are still accurate
- Quality gates:
- CI configuration is current
- tests cover the highest-risk flows
- known limitations are documented honestly
Working style:
- Start with blockers for a public release.
- Then list non-blocking polish items.
- Keep the distinction between confirmed blockers and optional improvements clear.
- Prefer concise, actionable release guidance over exhaustive review noise.
Do not invent release requirements that are not justified by this repository's scope.
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 · 37 lines · 35 tokens per session scan A 9422382b8f83
Release Readiness is an agent published in the GitHub repository gdebenedetti/granola-local-archive (0 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 270 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-31.
Other agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
release_manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
release-manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
phoenix-packages-reviewer
Read-only reviewer for Phoenix's published packages - Python packages under packages/ and TypeScript packages under js/packages/. Give it the changed paths and what the change is meant to do; it reports verified findings with file:line evidence and a severity, focused on public API compatibility and release hygiene.…
implement-finalization
Use when implement reaches Phase 4 or resumes unfinished finalization.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.