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.
git 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/rules/afaraha8403/balakit/base)<a href="https://agentmods.dev/rules/afaraha8403/balakit/base"><img src="https://agentmods.dev/badge/rules/afaraha8403/balakit/base/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/afaraha8403/balakit/base"><img src="https://agentmods.dev/badge/rules/afaraha8403/balakit/base.svg" alt="Reviewed on agentmods" width="80" 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.01644 | $0.01644 |
| Opus 5.5 | $0.00658 | $0.00658 |
| Sonnet 5.5 | $0.00329 | $0.00329 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
base 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- 1mo ago Changed · +6 lines · +304 tokens per session 103135e5ff66
- 1mo ago First seen · 87 lines · 1,340 tokens per session scan A 89006138d947
base is a cursor rule published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,644 tokens to every session, about $0.0066 per session on Opus 5.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 cursor rules, from other repositories
skill-creator
Create, edit, evaluate, and debug the skills in this repo, including running their evals and fixing a description that fails to trigger. Use when user says 'help me build a new skill', 'add a skill for X', 'run the evals for the tf skill', 'run the behavioral evals', 'my skill is not triggering', 'fix this skill's…
file-organization
Project file and folder organization patterns.
skill-router
Use before starting any task in Cursor to check whether a skill file must be read first. Routes PRD, test-writing and code-verification tasks to the skill path to read before writing code.
tf-plan
Review a Terraform plan before applying it: destroys and replacements of data-bearing resources, secrets readable in plan output, out-of-band drift, blast radius, and whether the apply is bound to the plan you actually reviewed. Use when user says 'review my plan', 'is this plan safe to apply', 'check tfplan', 'what…
clarify-first
Infer-and-act by default — ask only on high confusion weight, after inspecting, with a decision-linked question.
composer-senior-practices
Version-pinned framework guidance from primary docs when building on unfamiliar stacks, upgrading, or reviewing architecture — load when evidence beats training data; not required for routine feature work.