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/syncgit 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.00401 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
sync 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 yesterday.
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
sync
Generate paste-ready standup notes from git history, GitHub activity, and BRAIN.md context.
Usage
engineer-brain sync
What it does
- Determines lookback window (1 day, or 3 days on Monday)
- Runs
scan.shfor commits, branches, and (whenghis authenticated) PRs / reviews / releases (prefer text mode for sync; usescan.sh --jsonfor tooling/CI) - Reads BRAIN.md for sprint context and upcoming events
- Generates concise prose standup notes (not a commit dump)
Authored git commits alone are not enough — reviews, releases, demos, and
design-feedback work often only show up via gh, your tracker, or BRAIN.md.
Output format
1. What I worked on yesterday:
- [1–3 impact-focused bullets: reviews, tickets, releases, demos]
2. What I plan on working on today:
- [open PRs + tracker In Progress/Review + BRAIN events]
3. Blockers:
- None
Scanner config (optional)
In scan.sh:
| Variable | Purpose |
|---|---|
PERSONAL_REPOS |
Side-project basenames to exclude from team standup metrics |
GH_OWNERS |
Org names used to filter review results |
RELEASE_REPOS |
owner/name repos to check for recent releases |
Intelligence
- Monday-aware: Looks back 3 days on Mondays
- Weekend-aware: Tells you to take the day off on weekends
- Correction loop: If you paste a real standup that the sync missed, treat it as ground truth and update BRAIN.md
- Blocker detection: Flags merge conflicts, CI failures, stale branches when present
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.
- yesterday First seen · 54 lines · 0 tokens per session scan A b9f7f7d6ef2d
sync 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 401 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
specify
Create or update the feature specification from a natural language feature description.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
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…
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
execute
Executa o plano aprovado em .first-plan/07-state/plans/. Segue o plano à risca, para se algo invalidar premissa, gera relatório ao final.