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/sandeep-alluru/notarize/releasegit clone --depth 1 https://github.com/sandeep-alluru/notarizeWrote 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/sandeep-alluru/notarize/release)<a href="https://agentmods.dev/commands/sandeep-alluru/notarize/release"><img src="https://agentmods.dev/badge/commands/sandeep-alluru/notarize/release.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.00219 |
| Opus 5 | $0.00000 | $0.00110 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
release 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 2d 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.
This is a copy
100% identical to release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Prepare a release: bump version, finalize CHANGELOG, and show the git tag command.
Usage: /project:release (e.g. /project:release 0.2.0)
Steps:
- Verify all checks pass: lint, typecheck, tests (run make all)
- In CHANGELOG.md:
- Rename [Unreleased] to [] - <today's date in YYYY-MM-DD>
- Add a new empty [Unreleased] section at the top
- Update the comparison links at the bottom
- In pyproject.toml: set version = ""
- Show the git commands needed (do NOT run them):
git add CHANGELOG.md pyproject.toml git commit -m "chore: release v<version>" git tag v<version> git push origin main --tags - Note: the GitHub Actions release.yml will auto-publish to PyPI on tag push.
Do NOT push or tag without explicit user confirmation.
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.
- 2d ago First seen · 22 lines · 0 tokens per session scan A 7ec9d53abf43
release is a command published in the GitHub repository sandeep-alluru/notarize (0 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 219 tokens. A static security scan graded it A with 0 findings. It is 100% identical to release, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
audit-release-gate
Produce a machine-readable Solana release gate using the solana-audit release workflow and evidence-backed PASS, FAIL, or SKIP checks.
go-release
Command "go-release" from ready-to-release/eac, covering release, process, output and example usage.
CHANGELOG
All notable changes to eac-mcp-server will be documented in this file. The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
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.
release-now
Create a git tag + GitHub Release for open-pr — an official release if standing on main, an RC if standing on a branch with an open PR (a dev tool specific to this repo, not shipped in the plugin).