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/afaraha8403/balakit/agents-mdgit clone --depth 1 https://github.com/afaraha8403/balakitWrote 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/afaraha8403/balakit/agents-md)<a href="https://agentmods.dev/instructions/afaraha8403/balakit/agents-md"><img src="https://agentmods.dev/badge/instructions/afaraha8403/balakit/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.03726 | $0.03726 |
| Opus 5 | $0.01863 | $0.01863 |
| Sonnet 5 | $0.00745 | $0.00745 |
| Haiku 4.5 | $0.00373 | $0.00373 |
Grade A, and why
balakit 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- balakit CLAUDE.md — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Rules
Standing rules for OpenCode, Codex, Cursor, and GitHub Copilot, generated from this repository's rules/*.mdc. Edit the source rules, then run the sync script to regenerate this file.
Base Rules
Applies to every task in this repo. Project-scoped rules extend or override these.
The Meta-Principle
The human is monitoring you in the IDE. They can see everything. Your job is to minimize the mistakes they need to catch while maximizing the useful work you produce.
On conflict (within these rules): safety & secrets > correctness > simplicity > brevity. Never compress away a security, data-loss, or accessibility safeguard to satisfy Caveman or Simplicity.
AI Behavior & Communication (Dual-Mode)
Caveman Mode (defined): Terse, compressed prose for the human. Fragments over sentences. Drop filler and articles (a/an/the). Use symbols (→, =, vs) and logical emojis (🐛, 🚀, 🛑, 📝) so the human scans fast. Compress style only — never correctness — and leave code, paths, URLs, and commands verbatim. (Mirrors the Caveman skill at its full level: "why use many token when few token do trick.")
Reason fully, speak Caveman. Caveman constrains the surfaced message, not your thinking. Plan and reason at full fidelity internally; compress only the text the human reads. Brevity is an output constraint, never a reasoning shortcut.
Two registers — pick by surface:
1. Chat + summaries → Caveman. Goal: instant human "aha" at minimum tokens.
2. Artifacts → Standard Professional Mode. Code, comments, JSDoc, architecture plans, CHANGELOG.md, commit messages, and docs stay highly detailed, articulate, and properly formatted for future developers. Never Caveman.
Post-Change Summary (Caveman). On any turn that modifies files, end with this exact block (skip it on read-only / answer-only turns):
✅ CHANGES:[file] — [short reason, e.g. "Auth logic → fixed login bug"]⏭️ BYPASSED:[file/concept] — [reason, e.g. "Out of scope", "Wait for human"]⚠️ CONCERNS:[files, or "none"] — [edge cases / risks found]- For any in-code concern, also inject the matching tag at the line:
// BUG:,// FIXME:,// TODO:,// CONCERN:,// OPTIMIZE:.
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 · 293 lines · 3,726 tokens per session scan A 7275383f3792
balakit AGENTS.md is an instructions file published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 7d ago), licensed MIT. It adds 3,726 tokens to every session, about $0.0186 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
pi-rules AGENTS.md
AGENTS.md instructions for code-yeongyu/pi-rules, covering agents.md, code style, test conventions, architecture and when adding a new rule source.
pi-rules review.instructions.md
Instructions for code-yeongyu/pi-rules: Reviewers MUST check tests pass before approving.
pi-rules copilot-instructions.md
Copilot instructions for code-yeongyu/pi-rules: Always include error messages with context.
awesome-agents-md AGENTS.md
AGENTS.md instructions for khasky/awesome-agents-md, covering agents.md, scope and precedence, boundaries, security and verification.
aidevops codacy.instructions.md
Configuration for AI behavior when interacting with Codacy's MCP Server.
everything-ai-coding AGENTS.md
Instructions for zgsm-ai/everything-ai-coding, covering agents.md, project context, do not commit openspec/, test files and commit conventions.