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/metaspartan/cybara/agents-mdgit clone --depth 1 https://github.com/metaspartan/cybaraWrote 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/metaspartan/cybara/agents-md)<a href="https://agentmods.dev/instructions/metaspartan/cybara/agents-md"><img src="https://agentmods.dev/badge/instructions/metaspartan/cybara/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.01010 | $0.01010 |
| Opus 5 | $0.00505 | $0.00505 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
cybara AGENTS.md scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Prefer Bun-native APIs (`Bun.spawn`/`Bun.spawnSync`, `Bun.file`) over `child_process`/`fs` shell-outs. How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cybara Agent Rules
Rules for any AI agent or contributor working in this repo. Follow them exactly;
they override default habits. Deeper conventions live in CLAUDE.md.
Package Manager Policy (Strict)
- Bun is the only allowed JavaScript/TypeScript package manager and task runner.
- Always use Bun commands:
bun installbun add <pkg>bun remove <pkg>bun run <script>bun testbunx <tool>
- Never use
npm,npx,pnpm,yarn, orcorepack. - Treat
bun.lockas the canonical lockfile. - Prefer Bun-native APIs (
Bun.spawn/Bun.spawnSync,Bun.file) overchild_process/fsshell-outs.
Command Translation
- If docs or snippets mention npm-style commands, translate them to Bun equivalents before running.
- If a third-party instruction cannot run with Bun, stop and propose a Bun-compatible alternative.
TypeScript Type Safety
- Never use
any— not in signatures, casts, generics, oras any. It is banned. - Model real shapes with
interface/type. For genuinely unknown input useunknownand narrow it before use (type guards, discriminated unions). - Type every exported function's parameters and return value explicitly. Do not rely on inference across module boundaries.
- Avoid non-null assertions (
!). Handlenull/undefinedwith?.and??. - No
@ts-ignore/@ts-expect-errorto silence real errors — fix the type instead. If a third-party type is missing, declare a localinterfacefor the slice you use. - Keep functions and route handlers returning consistent, fully-typed API shapes
(snake_case fields for HTTP responses — see
CLAUDE.md).
No Comments
- Write code with no comments. Names and structure carry the meaning.
- Do not add header blocks, JSDoc, inline
//notes, or commented-out code. - Never reference other products, competitors, or external projects anywhere in code or comments.
- The rare exception is a short
/* ... */note only when logic is genuinely non-obvious and cannot be made clear by renaming or restructuring; default to none.
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 · 84 lines · 1,010 tokens per session scan A c2db4f1b77cb
cybara AGENTS.md is an instructions file published in the GitHub repository metaspartan/cybara (25 stars, last pushed today), licensed MIT. It adds 1,010 tokens to every session, about $0.0051 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
m2e CLAUDE.md
Instructions for sammcj/m2e, covering claude.md, project overview, core architecture, main components and key files.
zeroclaw CLAUDE.md
Claude Code instructions for zeroclaw-labs/zeroclaw, covering claude.md — zeroclaw (claude code), claude code settings, hooks and slash commands.
nuwax AGENTS.md
AGENTS.md instructions for nuwax-ai/nuwax, covering ai agent system documentation, 系统概述, ai agent 架构, 核心组件 and ai 功能特性.
AgentEval copilot-instructions.md
Copilot instructions for AgentEvalHQ/AgentEval, covering agenteval - ai coding agent instructions, architecture overview, environment setup, optional: secondary models for comparison and build & test commands.
AgentEval tracing.instructions.md
Guidelines for implementing trace recording and replay.
hands-on-modern-rl AGENTS.md
AGENTS.md instructions for walkinglabs/hands-on-modern-rl, covering repository guidelines, project structure, commands, editing rules and tikz → svg workflow.