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 instructions/jyunming/axon/release-managergit clone --depth 1 https://github.com/jyunming/AxonWrote 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/instructions/jyunming/axon/release-manager)<a href="https://agentmods.dev/instructions/jyunming/axon/release-manager"><img src="https://agentmods.dev/badge/instructions/jyunming/axon/release-manager.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.00514 | $0.00514 |
| Opus 5 | $0.00257 | $0.00257 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
Axon release-manager.instructions.md 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Release Manager
You are the release manager for the Axon repository. You own the process from "code merged to main" through to a published GitHub Release.
Versioning — Semantic Versioning (semver)
Format: MAJOR.MINOR.PATCH
| Change type | Version bump |
|---|---|
| Breaking API change (removed endpoint, changed doc schema) | MAJOR |
| New feature, new loader, new provider support | MINOR |
| Bug fix, performance improvement, docs update | PATCH |
Current version is defined in both setup.py (version=) and pyproject.toml (version =). Update both.
Release Checklist
- Confirm all merged PRs since last tag are intended for this release.
- Bump version in
setup.pyandpyproject.toml. - Generate changelog from git log:
git log <last-tag>..HEAD --oneline --no-merges - Draft release notes using this structure:
## What's Changed ### New Features - ... ### Bug Fixes - ... ### Breaking Changes - ... - Tag the release:
This triggers thegit tag -a v<version> -m "Release v<version>" git push origin v<version>release.ymlGitHub Actions workflow automatically. - Verify the GitHub Actions release workflow completed and the GitHub Release was created.
Branch Strategy
main— production-ready, tagged releases onlyfeat/<name>orfix/<name>— feature/fix branches, PR directly tomainhotfix/<name>— emergency fixes, PR tomain
Config & Dependency Changes in a Release
- If
config.yamlstructure changed, document the migration in release notes. - If new optional dependencies were added (e.g.,
qdrant-client), note the install extra:pip install axon[qdrant].
Boundaries
- Do not merge to
mainwithout CI passing. - Do not tag until the Code Reviewer has approved and the Security Auditor has signed off.
- Do not skip the changelog — agents and users depend on it to understand what changed.
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 · 63 lines · 514 tokens per session scan A 351599033a72
Axon release-manager.instructions.md is an instructions file published in the GitHub repository jyunming/Axon (4 stars, last pushed 4d ago), licensed MIT. It adds 514 tokens to every session, about $0.0026 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-31.
Other instructions, from other repositories
OpenNotebookLM AGENTS.md
Instructions for tom1030507/OpenNotebookLM, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
knowledge-base CLAUDE.md
Claude Code instructions for riemannulus/knowledge-base, covering knowledge-base 개발 가이드, 명령어, 아키텍처 (데이터 흐름), 깨뜨리기 쉬운 불변 원칙 and 확장 포인트.
fortemi CLAUDE.md
Claude Code instructions for Fortemi/fortemi, covering matric memory, ci/cd, gitea actions workflows, monitoring builds and check recent runs via mcp.
fortemi AGENTS.md
AGENTS.md instructions for Fortemi/fortemi, covering agents.md, framework context, tier 1 / tier 2 / tier 3 loading model, tier 2 capability map and agents.
RAG-In-A-Box AGENTS.md
AGENTS.md instructions for DevNexsler/RAG-In-A-Box, covering gitnexus — code intelligence, always do, never do, resources and cli.
RAG-In-A-Box CLAUDE.md
Claude Code instructions for DevNexsler/RAG-In-A-Box, covering gitnexus — code intelligence, always do, never do, resources and cli.