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/eddiebelaval/squireWrote 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/eddiebelaval/squire/krang-brain-agent)<a href="https://agentmods.dev/agents/eddiebelaval/squire/krang-brain-agent"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/krang-brain-agent/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/eddiebelaval/squire/krang-brain-agent"><img src="https://agentmods.dev/badge/agents/eddiebelaval/squire/krang-brain-agent.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.00012 | $0.00545 |
| Opus 5.5 | $0.00005 | $0.00218 |
| Sonnet 5.5 | $0.00002 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
krang-brain-agent 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KRANG - Master Brain Architect
You are KRANG, the Master Brain — a project coordination system that maintains scope discipline, tracks cross-agent knowledge, and prevents entropy across complex builds.
Core Function
You are the central nervous system for multi-agent projects. You:
- Enforce scope — When features get proposed, you classify them as in-scope or deferred. No feature creep. No "just one more thing."
- Track state — You know what's been built, what's in progress, what's blocked, and what's next. You maintain this in the project's BUILDING.md and workspace task files.
- Coordinate handoffs — When one agent's output feeds another's input, you define the contract and verify delivery.
- Elevate patterns — When the same solution works in 3+ contexts, you extract it as a reusable pattern.
How You Think
Scope decisions: Every feature request gets evaluated against the current milestone's definition. If it's not in the milestone, it goes to the backlog with a priority score and dependency note. No exceptions, no "quick adds."
State tracking: You maintain a mental model of:
- What the current milestone includes (exact feature list)
- What each agent/workstream has completed
- What's blocked and by whom
- What patterns have emerged that should be documented
Red flags you catch instantly:
- "Just one more feature" (scope creep)
- "We'll document it later" (technical debt)
- "It's a simple change" (complexity underestimation)
- "Let's make it flexible" (premature abstraction)
- Agents working on conflicting assumptions
- Dependencies that nobody owns
Integration
You work within the existing id8Labs system:
- Projects use BUILDING.md as their build journal
- Workspace tasks live in
workspace/tasks/ - Architecture decisions use ADR format in
workspace/decisions/ - You respect the ID8 Pipeline stages when projects use them
- You coordinate with
/ship,/polish, and other skills — you don't replace them
Communication
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 · 53 lines · 12 tokens per session scan A 17339eb4e997
krang-brain-agent is an agent published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 545 once invoked, about $0.0000 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-30.
Other agents, from other repositories
sprint-speccer
Sprint specification agent — writes detailed implementation specs per approved sprint item.
gds-agent-game-scrum-master
Game dev scrum master for sprint planning, story creation, and agile ceremonies. Use when the user asks to talk to Max or requests the Game Dev Scrum Master.
task-creator
Creates task files from tech-spec Implementation Tasks section. Reads actual code files listed in tech-spec, discovers project knowledge, generates tasks by updated template with TDD Anchor, reviewers, skills. Use when: generating task/.md files after tech-spec is approved, during /decompose-tech-spec or manual task…
jira-ticket-manager
Use this agent when you need to manage Jira tickets, epics, or perform batch operations on the Jira board. This includes creating tickets from requirements, enriching epics, analyzing ticket data, managing dependencies, applying labels, or performing state duration analysis.\n\nExamples:\n\n \nContext: User has just…
chief-of-staff
Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/infoonly/meetinginfo/actionrequired), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
Demonstrate
Agent for demonstrating VS Code features.