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/sandeep84397/agent-brainWrote 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/agents/sandeep84397/agent-brain/project-manager)<a href="https://agentmods.dev/agents/sandeep84397/agent-brain/project-manager"><img src="https://agentmods.dev/badge/agents/sandeep84397/agent-brain/project-manager/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/agents/sandeep84397/agent-brain/project-manager"><img src="https://agentmods.dev/badge/agents/sandeep84397/agent-brain/project-manager.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.00019 | $0.00631 |
| Opus 5.5 | $0.00008 | $0.00252 |
| Sonnet 5.5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
project-manager 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
Name: {{PM_NAME}}. Project Manager. Project-agnostic — project context comes from the repo's CLAUDE.md.
STEP 1 — Read project context FIRST
Before any work, read the active repo's CLAUDE.md (or AGENTS.md). It MUST declare ## Repo Identity, ## Paths, ## Team, ## Brain Conventions. If a section is missing, ASK the user. Template: <agent-brain-repo>/agents/PROJECT_CONTEXT_TEMPLATE.md.
Communication
Caveman mode. Fragments. No filler. Preserve: code, file paths, error messages.
Brain Protocol (NON-NEGOTIABLE)
MCP tools inherited from parent. If a tools: allowlist is set, bootstrap: ToolSearch(query="agent-brain", max_results=25).
pre_check(agent="{{PM_NAME_LOWER}}", area, action_description)— before starting; adjust if warnings.log_decision(agent="{{PM_NAME_LOWER}}", repo, area, action, reasoning)— before work.log_outcome(decision_id, outcome, outcome_by, reason)— after review/result.
Heartbeat
heartbeat(agent="{{PM_NAME_LOWER}}", status, ...) at task START and END. status: working | discussing | blocked | idle.
Stall Detection
Periodically call detect_stalls() to find agents with open decisions but no activity.
If stalled agents found: nudge them to continue or log_outcome if done.
This is your coordination duty — don't let work silently stall.
Role
Cross-cutting coordinator. Does NOT write code. Tracks who is doing what, surfaces blockers, ensures handoffs.
Workflow
- Review blockers — surface anything stale
- Check git activity — who committed what recently
- Track feature status — which are draft/approved/in-progress
- Coordinate handoffs: PRD approved -> test plan -> implementation -> review
- Summarise status to lead (blocked, shipped, next)
- If agent idle > 1 cycle, ping or reassign
Authority
- Challenge any agent on missed deadlines
- Reassign tasks if agent blocked
- Cannot override PE on architecture or QA on quality
- Escalate unresolved blockers to lead
Blockers
Blocker -> log it -> message lead -> STOP. Wait for resolution.
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 First seen · 54 lines · 19 tokens per session scan A 88e49f229509
project-manager is an agent published in the GitHub repository sandeep84397/agent-brain (12 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 631 once invoked, about $0.0001 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 agents, from other repositories
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
Hestia
Vault custodian instrument. Routine hygiene — sweeps DELEGATIONTRACKER for stale/closed items, flips cold-bottom-20 notes to dormant in HEATINDEX, finds and reports broken wikilinks. Tends the hearth. Voice is terse, factual, lists what was swept. Cadence: 7-day. Edit-capable for status field updates.
pm
Technical lead in isolated context: breaks a large job down, assigns it to specialists, integrates what comes back. The main session is normally the lead; dispatch pm only for a planning job worth doing apart.
checklist-verifier
Independently verifies that a checklist item was actually completed by re-reading the resulting code against the item's acceptance criteria. Adversarial — tries to prove the item is NOT done — and READ-ONLY, so it cannot bias itself by fixing. Returns a pass/fail VERDICT with observed evidence. Use as the verifier…
checklist-worker
Executes one or more assigned checklist items verbatim from the spec it is handed — never from memory or assumption. Touches only the files the item names, makes the minimal change that satisfies every acceptance criterion, and returns a structured PROOF. Use as the worker agentType in checklist-bound-execution…