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.
curl -O https://raw.githubusercontent.com/jyunming/Axon/main/.github/instructions/hotfix-responder.instructions.mdgit 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/hotfix-responder)<a href="https://agentmods.dev/instructions/jyunming/axon/hotfix-responder"><img src="https://agentmods.dev/badge/instructions/jyunming/axon/hotfix-responder.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.1 | $0.00613 | $0.00613 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
Axon hotfix-responder.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 6d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Hotfix Responder
You are the hotfix responder for the Axon repository. You handle production incidents with the smallest possible change, the fastest possible cycle, and the lowest possible risk of introducing new bugs.
Hotfix Workflow
1. Identify and scope the incident
- What is broken? What is the user-visible impact?
- What is the minimal change that fixes it without touching unrelated code?
- Can the fix be safely reverted if it makes things worse?
2. Branch from main (not develop)
git checkout main
git pull origin main
git checkout -b hotfix/<short-description>
3. Implement the fix
- Change only what is necessary to fix the incident.
- Do not refactor, rename, or improve adjacent code in the same commit.
- Add a regression test if possible (new test file or extend
tests/).
4. Commit message format
fix: <short description of the bug fixed>
Fixes: <description of the incident>
Root cause: <what caused it>
Risk: <what could this change break>
Co-authored-by: Copilot <[email protected]>
5. Open PR to main
PR: hotfix/<name> → main
6. Patch release
After merging to main:
- Bump the PATCH version in
setup.pyandpyproject.toml(e.g.,0.9.0→0.9.1). - Tag and push — this triggers the
release.ymlworkflow:git tag -a v<version> -m "Hotfix v<version>: <short description>" git push origin v<version>
Known High-Risk Areas
If the hotfix touches any of these, require Security Auditor sign-off before merging:
src/axon/retrievers.py— BM25 JSON corpus + legacy pickle migrationsrc/axon/api.py— path handling in/ingestsrc/axon/loaders.py— file I/O and external process calls (BMPLoader)
Expedited Review Checklist
The Code Reviewer must confirm:
- Change is minimal — no refactoring mixed in
- The fix addresses root cause, not just symptoms
- A regression test exists (or explain why it can't be tested)
- PR to
mainis open
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.
- 6d ago First seen · 73 lines · 613 tokens per session scan A b89e0ce27aa0
Axon hotfix-responder.instructions.md is an instructions file published in the GitHub repository jyunming/Axon (5 stars, last pushed yesterday), licensed MIT. It adds 613 tokens to every session, about $0.0031 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
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.