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 commands/hrithik-gavankar/brainstack/updategit clone --depth 1 https://github.com/Hrithik-Gavankar/brainstackWhat 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.00000 | $0.00154 |
| Opus 5 | $0.00000 | $0.00077 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
update 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 2d 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.
What it actually says
update
Refresh BRAIN.md with latest git data, patterns, and metrics.
Usage
engineer-brain update
What it does
- Scans all repos for the last 30 days
- Reads current BRAIN.md
- Updates every section with fresh data
- Writes the updated BRAIN.md
- Prints a change summary
Sections updated
- Active Repositories (commit counts, last-active dates)
- Expertise Map (reclassified from commit patterns)
- Work Patterns (commit type distribution, velocity)
- Current Sprint Context (active branches, achievements)
- Growth Areas (progress check)
Recommended frequency
Monthly, or after major project changes.
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.
- 2d ago First seen · 34 lines · 0 tokens per session scan A b2eaac9fe91d
update is a command published in the GitHub repository Hrithik-Gavankar/brainstack (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 154 tokens. 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 commands, from other repositories
add-portal
You are helping the user build a job-portal search skill for a job board in their market. The repo ships worked examples of the pattern (four Danish portals plus the country-agnostic linkedin-search and freehire-search), and the README invites users elsewhere to build equivalents — this command turns that invitation…
html-report
Generate a self-contained HTML dashboard from jobsearchtracker.csv and the application archives under documents/applications/. The output is a single .html file — no server, no dependencies — that can be opened directly in a browser.
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
OpenSpec: Apply
Implement an approved OpenSpec change and keep tasks in sync.
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
daily
/jobs daily is the main orchestrator. It runs the daily sequence end to end with no between-step prompts. Empty steps are auto-skipped.