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 skills add Hrithik-Gavankar/brainstack --skill engineer-braingit 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/skills/hrithik-gavankar/brainstack/engineer-brain)<a href="https://agentmods.dev/skills/hrithik-gavankar/brainstack/engineer-brain"><img src="https://agentmods.dev/badge/skills/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/skills/hrithik-gavankar/brainstack/engineer-brain"><img src="https://agentmods.dev/badge/skills/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.00133 | $0.04508 |
| Opus 5.5 | $0.00053 | $0.01803 |
| Sonnet 5.5 | $0.00027 | $0.00902 |
| Haiku 4.5 | $0.00013 | $0.00451 |
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 18d 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
engineer-brain — Self-Updating Engineering Context
A living system that learns how you work, what you focus on, where you're growing, and where you should push further. Produces actionable output for daily syncs and quarterly reviews.
Data Sources
- Git history across repos in your workspace
- GitHub activity via
gh(authored PRs, reviews, releases/tags) — often more accurate than local commits alone - BRAIN.md at
${SKILL_DIR}/BRAIN.md(the living document) - Agent transcripts in the Cursor projects folder (demos, skill work, non-commit tasks)
- Jira — Cursor: Atlassian MCP (marketplace plugin, required for
sync). Other platforms:jira.shCLI whenJIRA_*env is set. - Linear / other trackers via integration skill (if available)
Critical: Standup-relevant work is frequently not in authored git commits.
Reviews, releases, demos, office-hours/meetup prep, cross-team notifications, and
design-feedback incorporation must be pulled from GitHub/Jira/transcripts/BRAIN —
not inferred from git log --author alone.
Commands
Parse the user's request to determine which command to run:
sync (daily standup helper)
Generate today's standup notes.
Scope: Current team and current role only.
Only include work from team repos / team activities in this workspace.
Never reference past roles or personal/side projects — this is for your
team's standup thread. Repos listed in PERSONAL_REPOS inside scan.sh
are excluded from team standup scope.
Schedule: Workdays only (Monday–Friday). If today is Monday, "yesterday" means last Friday. If today is a weekend, skip — standups don't happen on weekends.
- Determine the lookback window based on the day of week:
- Monday: Friday only — ignore Saturday and Sunday; 3-day scan for data,
filter standup bullets and
ghto Friday-dated activity only - Tuesday–Friday: scan last 1 day
- Saturday/Sunday: tell the user "No standup today — it's the weekend." and stop.
bash "${SKILL_DIR}/scripts/scan.sh" "$HOME/path/to/workspace" [1 or 3] - Monday: Friday only — ignore Saturday and Sunday; 3-day scan for data,
filter standup bullets and
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 18d ago Changed · +14 lines 4a2fc983a086
- 1mo ago Changed · +21 lines 3aca9fea1306
- 1mo ago First seen · 395 lines · 133 tokens per session scan A 0e1ff5c3a2d7
engineer-brain is a skill published in the GitHub repository Hrithik-Gavankar/brainstack (24 stars, last pushed 19d ago), licensed MIT. It adds 133 tokens to every session and 4,508 once invoked, about $0.0005 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 skills, from other repositories
wiki-dashboard
Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.
wiki-switch
List, create, or switch named Obsidian wiki vault profiles under the global config directory. Use when changing the active vault, checking which vault is active, or managing multi-vault profiles.
daily-update
Run or configure the daily wiki maintenance cycle: check source freshness, refresh the index and hot.md, and manage its scheduled 9 AM launchd/systemd/cron reminder. Use for daily or morning wiki refresh or scheduler setup and verification.
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
ambient-context-catch-me-up
Use when the user asks what they were doing, where they got to, what is still open, or to be caught up after a break. Reads today's Ambient Context summary and record and briefs them.
kb-memory
Use when knowledge base and memory system for AI agents. Covers company KB, persistent memory, session recall, and brain architecture for context preservation.