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/Hrithik-Gavankar/brainstackWrote 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/hrithik-gavankar/brainstack/engineer-brain)<a href="https://agentmods.dev/rules/hrithik-gavankar/brainstack/engineer-brain"><img src="https://agentmods.dev/badge/rules/hrithik-gavankar/brainstack/engineer-brain/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/hrithik-gavankar/brainstack/engineer-brain"><img src="https://agentmods.dev/badge/rules/hrithik-gavankar/brainstack/engineer-brain.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.00622 | $0.00622 |
| Opus 5.5 | $0.00249 | $0.00249 |
| Sonnet 5.5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
engineer-brain 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstack Context
You are assisting [YOUR NAME], a [YOUR ROLE] at [YOUR COMPANY], with [X]+ years of industry experience.
Career Context
- Current role ([START DATE]–): [Role title] — [brief description of what you do]
- Previous role ([DATES]): [Role] — [technologies, key achievements]
- Before that ([DATES]): [Role] — [technologies, key achievements]
- Goal: [Your career goal, e.g. "Become a Staff Engineer", "Transition to ML Engineering"]
Full Skills Inventory
- Backend: [Languages, frameworks, databases you use]
- Frontend: [UI frameworks, CSS tools, design systems]
- Infrastructure: [CI/CD, cloud, containers, orchestration]
- Current focus: [What you're actively learning/building]
Workspace Layout
[Brief description of your repo structure — e.g. "Monorepo with 5 packages" or "12 microservice repos"]
Engineering Profile
- Strongest in: [Your top 3-5 technical strengths with context]
- Growing in: [Areas you're actively developing]
- Underused skills: [Skills proven elsewhere but not applied in current role]
- Work style: [Your patterns — e.g. "test-driven", "prototype-first", "documentation-heavy"]
- Peak hours: [When you do your best work]
When Helping Me
- [Instruction for the AI — e.g. "Be aware of my multi-repo context"]
- [Instruction — e.g. "Push me toward architecture ownership"]
- [Instruction — e.g. "Reference my existing test patterns when writing tests"]
- [Instruction — e.g. "Flag security implications proactively"]
- [Instruction — e.g. "Remind me to leverage underused skills"]
- For standups:
/engineer-brain sync(always pulls Jira — setup) | Quarterly:/engineer-brain quarterly| Health:/engineer-brain doctor| PR digest:/engineer-brain watch - For shared spikes/epics:
/team-brain attach <id>| capture findings | breakdown stories — never mix personal BRAIN.md into team initiative files
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 · +21 tokens per session 127bcee8a331
- 1mo ago First seen · 52 lines · 601 tokens per session scan A 53429be9b436
engineer-brain is a cursor rule published in the GitHub repository Hrithik-Gavankar/brainstack (24 stars, last pushed 16d ago), licensed MIT. It adds 622 tokens to every session, about $0.0025 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
checkpoint
Persistent memory archival — save discoveries to prevent amnesia across sessions.
aimemo
aimemo persistent memory instructions.
memory-rules.mdc
Cursor rule "memory-rules.mdc" from devviniuchita/memory-system, covering 🧠 neural memory system, 🚀 execution patterns, pattern: problem decomposition, pattern: continuous delivery and 🔄 self-improvement loop.
ai-kb
Use shared AI KB rules and context.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.