agentmods.dev

Axon: Instructions file for GitHub Copilot

.github/instructions/release-manager.instructions.md

Axon release-manager.instructions.md is an instructions file for GitHub Copilot from jyunming/Axon. It costs 514 tokens per session, scanned A, original, MIT.

A set of instructions for managing software releases in the Axon repository. It covers semantic versioning, where each version number signals the size of a change, plus the checklist from merged code to a published GitHub release.

In plain words
What is it for?
Use it to choose version bumps, update setup.py and pyproject.toml, generate changelogs, write release notes, create Git tags, and verify the release workflow.
Why use it?
It reduces missed release steps, inconsistent version numbers, and unclear release notes. It also explains which branch and files to update when preparing a release.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is jyunming/Axon's own configuration. It tells GitHub Copilot how to work on Axon itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Axon configures →

not rated 4repo 28d ago A scan 514 tokens original MIT
View source ↗ jyunming/Axon jyunming.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to jyunming/Axon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jyunming/Axon/main/.github/instructions/release-manager.instructions.md
Clone the repo
git clone --depth 1 https://github.com/jyunming/Axon

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for Axon release-manager.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jyunming/axon/release-manager/github.svg)](https://agentmods.dev/instructions/jyunming/axon/release-manager)
Your own site
<a href="https://agentmods.dev/instructions/jyunming/axon/release-manager"><img src="https://agentmods.dev/badge/instructions/jyunming/axon/release-manager/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.

agentmods 80×15 button for Axon release-manager.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jyunming/axon/release-manager"><img src="https://agentmods.dev/badge/instructions/jyunming/axon/release-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 514 This file is loaded in full into every session.
When invoked 514 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00514 $0.00514
Opus 5.5 $0.00206 $0.00206
Sonnet 5.5 $0.00103 $0.00103
Haiku 4.5 $0.00051 $0.00051

Measured 1mo ago against content hash 351599033a72, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.github/instructions/release-manager.instructions.md · 63 lines

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

  1. Confirm all merged PRs since last tag are intended for this release.
  2. Bump version in setup.py and pyproject.toml.
  3. Generate changelog from git log: 
    git log <last-tag>..HEAD --oneline --no-merges
  4. Draft release notes using this structure: 
    ## What's Changed
### New Features
- ...
### Bug Fixes
- ...
### Breaking Changes
- ...
  5. Tag the release: 
    git tag -a v<version> -m "Release v<version>"
git push origin v<version>
    This triggers the release.yml GitHub Actions workflow automatically.
  6. Verify the GitHub Actions release workflow completed and the GitHub Release was created.

Branch Strategy

  • main — production-ready, tagged releases only
  • feat/<name> or fix/<name> — feature/fix branches, PR directly to main
  • hotfix/<name> — emergency fixes, PR to main

Config & Dependency Changes in a Release

  • If config.yaml structure 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 main without 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.

Read the full file on GitHub · 63 lines

Changes

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.

  1. 1mo ago First seen · 63 lines · 514 tokens per session scan A 351599033a72

Subscribe to this mod's changes

Axon release-manager.instructions.md is an instructions file published in the GitHub repository jyunming/Axon (4 stars, last pushed 28d ago), licensed MIT. It adds 514 tokens to every session, about $0.0021 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.

Claude CodeGit and workflowReleasesembeddingsfastapigraphraghybrid-searchknowledge-base
Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens