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/spillwavesolutions/agent-brain/ag-brain-releasegit clone --depth 1 https://github.com/SpillwaveSolutions/agent-brainWrote 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/spillwavesolutions/agent-brain/ag-brain-release)<a href="https://agentmods.dev/commands/spillwavesolutions/agent-brain/ag-brain-release"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/agent-brain/ag-brain-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.00735 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
ag-brain-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-brain-release
Release automation for Agent Brain packages.
Arguments
-
<bump>(required): Version bump typemajor- Breaking changes (1.2.0 → 2.0.0)minor- New features (1.2.0 → 1.3.0)patch- Bug fixes (1.2.0 → 1.2.1)
-
--dry-run(optional): Preview changes without executing
Examples
/ag-brain-release patch
/ag-brain-release minor
/ag-brain-release major
/ag-brain-release minor --dry-run
Task
Execute a versioned release with these steps:
Pre-Release Checks (MUST PASS)
- Working directory is clean (
git status --porcelainempty) - On
mainbranch - Synced with remote origin/main
- CLI dependency points to PyPI (not path) - flip if needed
- CHANGELOG entry exists for the new version. Calculate the new version from current + bump type, then verify
docs/CHANGELOG.mdcontains a## [X.Y.Z]heading matching it. If missing, abort with: "Add a## [X.Y.Z] - YYYY-MM-DDsection to docs/CHANGELOG.md and commit it before re-running. See the existing [10.0.0] entry for the expected Keep-a-Changelog format."
Note:
task before-pushis wrapped by an automatic lock-drift guard (scripts/before_push_lock_guard.sh, see issue #174). The guard snapshots cleanagent-brain-{server,cli}/poetry.lockfiles at task entry and reverts any in-task churn on exit. The release flow inherits this protection — no separate manualgit checkout HEAD -- poetry.lockstep is required aftertask before-push.
Release Steps
- Calculate new version from current + bump type (also used by pre-release check #5)
- Flip CLI dependency to PyPI if path-based
- Update version in 9 files:
agent-brain-server/pyproject.tomlagent-brain-server/agent_brain_server/__init__.pyagent-brain-cli/pyproject.tomlagent-brain-cli/agent_brain_cli/__init__.pyagent-brain-uds/pyproject.tomlagent-brain-uds/agent_brain_uds/__init__.pyagent-brain-mcp/pyproject.tomlagent-brain-mcp/agent_brain_mcp/__init__.pyagent-brain-plugin/.claude-plugin/plugin.json(top-level"version"field — must match CLI/server)
- Commit:
chore(release): bump version to X.Y.Z - Tag:
vX.Y.Z - Push branch and tag
- Create GitHub release (triggers PyPI publish)
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.
- 3d ago First seen · 74 lines · 0 tokens per session scan A 55c54edfd27d
ag-brain-release is a command published in the GitHub repository SpillwaveSolutions/agent-brain (117 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 735 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.
submit_to_list
Fork an external GitHub repo, add an entry to a curated list (e.g. awesome-), and open a PR — all via gh CLI.