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/openclosed-org/axum-harness/agents-mdgit clone --depth 1 https://github.com/openclosed-org/axum-harnessWrote 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/openclosed-org/axum-harness/agents-md)<a href="https://agentmods.dev/instructions/openclosed-org/axum-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/openclosed-org/axum-harness/agents-md.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.01883 | $0.01883 |
| Opus 5 | $0.00941 | $0.00941 |
| Sonnet 5 | $0.00377 | $0.00377 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
axum-harness AGENTS.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 5d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Thin coordination protocol for this repository. Keep this file stable, short, and cross-cutting. Put volatile plans in
docs/_local/.
1. Language
Communication MUST be Chinese.
Code, commands, config keys, logs, and protocol fields stay in their original language.
2. Repository Identity
This repository is an agent-first distributed backend harness template.
Default backend anchor: counter-service.
Business reference chain:
service -> contracts -> server -> outbox -> relay -> projector.
Engineering reference chain:
declared platform metadata -> secrets shape -> deploy shape -> GitOps direction -> runbook/gate evidence.
Root backend-core commands MUST NOT depend on optional frontend, desktop, mobile, or UI shell surfaces by default.
Backend deployable secrets use SOPS + age as the canonical shape. Local processes use just sops-run; single-VPS systemd-binary and optional prebuilt Podman application profiles use transient host env-files from just sops-export-env; cluster paths use Kustomize/Flux. Do not make .env the backend reference path.
Runtime hosts do not compile first-party Rust code. Single-VPS paths are binary-first by default; Podman primarily manages opt-in official resource containers such as SurrealDB, NATS, Valkey, MinIO, auth, and observability components. Low-resource presets may use embedded, in-process, local, or managed backends with explicit semantic limits. PostgreSQL is not the repository reference backend; current database lanes prioritize embedded libSQL/SQLite, optional Turso Cloud, and optional SurrealDB.
3. Operating Posture
Act as a senior distributed-systems engineer in a long-lived codebase.
Default rules:
- Read before changing.
- Understand the invariant before touching code.
- Fix the smallest causal closed loop, not the nearest symptom.
- Prefer simple, explicit, typed, testable code.
- Do not add speculative features, abstractions, compatibility layers, or configurability.
- Touch only lines required by the task.
- Match existing style.
- Do not hand-edit generated artifacts.
- Surface uncertainty instead of guessing.
- Verification not executed must not be reported as passed.
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.
- 5d ago First seen · 213 lines · 1,883 tokens per session scan A f4d830353177
axum-harness AGENTS.md is an instructions file published in the GitHub repository openclosed-org/axum-harness (49 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,883 tokens to every session, about $0.0094 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-30.
Other instructions, from other repositories
go-micro CLAUDE.md
Claude Code instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
go-micro AGENTS.md
AGENTS.md instructions for micro/go-micro, covering repository agent instructions and pull requests from codex tasks.
nacos AGENTS.md
AGENTS.md instructions for alibaba/nacos, covering agents.md, ai contribution guidelines, repository overview, core architecture and build & test commands.
camel AGENTS.md
AGENTS.md instructions for apache/camel, covering apache camel - ai agent guidelines, project info, ai agent rules of engagement, attribution and pr volume.
qiankun AGENTS.md
Instructions for umijs/qiankun, covering qiankun project knowledge base, structure, architecture (big picture), commands and build (vite 8 → package javascript; tsc → declarations).
qiankun CLAUDE.md
Instructions for umijs/qiankun: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.