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/brcampidelli/chimera-agent/agents-mdgit clone --depth 1 https://github.com/brcampidelli/chimera-agentWrote 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/brcampidelli/chimera-agent/agents-md)<a href="https://agentmods.dev/instructions/brcampidelli/chimera-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/brcampidelli/chimera-agent/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.00960 | $0.00960 |
| Opus 5 | $0.00480 | $0.00480 |
| Sonnet 5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
chimera-agent 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 4d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repository
A routing document. It is short on purpose — it tells you where the real rules live and states the few that have bitten us hard enough to be worth repeating.
Chimera is a Python agent framework (chimera/) with a Tauri + React desktop app
(apps/desktop/). ~41k lines of source, ~25k lines of tests, 1848 tests, mypy strict.
Where the rules live
| Working on | Read first |
|---|---|
| Desktop UI, styling, motion | apps/desktop/DESIGN.md |
| Anything user-facing | CONTRIBUTING.md |
| Security-sensitive code | SECURITY.md |
| Benchmarks and claims | bench/*/RESULTS.md and the matching PREREGISTRATION.md |
Hard rules
Never rename or delete an i18n key. apps/desktop/src/lib/i18n.tsx carries every language the
app offers, and the component tests assert on rendered English strings. A rename breaks them
silently in all of them at once. Adding keys is free; renaming is not.
A route change and its generated types ship in the same commit. If you touch a FastAPI route in
chimera/api/, regenerate both or CI fails on drift:
python -m chimera.api.schema_dump > apps/desktop/openapi.json
npm --prefix apps/desktop run gen:api
Run the full Python suite, not the module you touched. Per-module runs have let regressions
reach main here before. On Windows, run it in WSL.
Never weaken a test to make it pass. If a test asserts something false, say so and rewrite it
with the reasoning in the commit message — one in test_agent.py asserted that a run which called
no tool had done the work. Deleting the assertion and fixing the premise look identical in a diff
and are opposites in intent.
Numbers in bench/ are pre-registered. Predictions and readings are committed before a run
and never loosened afterwards. A retraction is published with the same prominence as the original
claim. If a result kills a claim, that is the result.
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.
- 4d ago First seen · 87 lines · 960 tokens per session scan A ecdc61492f25
chimera-agent AGENTS.md is an instructions file published in the GitHub repository brcampidelli/chimera-agent (20 stars, last pushed today), licensed Apache-2.0. It adds 960 tokens to every session, about $0.0048 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
mcp-devtools CLAUDE.md
Claude Code instructions for sammcj/mcp-devtools, covering claude.md, commands, build and run, testing and code quality.
AGI-Alpha-Agent-v0 AGENTS.md
META‑AGENTIC α‑AGI 👁️✨ — Mission 🎯 End‑to‑end: Identify 🔍 → Out‑Learn 📚 → Out‑Think 🧠 → Out‑Design 🎨 → Out‑Strategise ♟️ → Out‑Execute ⚡.
goal-flight AGENTS.md
AGENTS.md instructions for simonrowland/goal-flight, covering agent notes, goal flight routing, project commands (this repo), git workflow (this repo) and git-visible trigger hygiene.
ts AGENTS.md
AGENTS.md instructions for agentproto/ts, covering agent instructions for this repo, definition of done for agent sessions and recipes: gates you can declare today.
goal-flight CLAUDE.md
Claude Code instructions for simonrowland/goal-flight, covering claude code notes and git-visible trigger hygiene.
elephant-agent copilot-instructions.md
Copilot instructions for agentic-in/elephant-agent, covering github copilot instructions, source of truth order, review priorities, harness-specific checks and validation expectations.