Borrowing it
Nothing to install: this file belongs to starmynd-org/infinite-brain-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/starmynd-org/infinite-brain-os/main/.claude/agents/infinite-brain-architect.mdgit clone --depth 1 https://github.com/starmynd-org/infinite-brain-osWrote 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/starmynd-org/infinite-brain-os/infinite-brain-architect)<a href="https://agentmods.dev/agents/starmynd-org/infinite-brain-os/infinite-brain-architect"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/infinite-brain-architect/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/starmynd-org/infinite-brain-os/infinite-brain-architect"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/infinite-brain-architect.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.00035 | $0.01779 |
| Opus 5 | $0.00017 | $0.00890 |
| Sonnet 5 | $0.00007 | $0.00356 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
infinite-brain-architect 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 11d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
infinite-brain-architect
A specialist architect for turning fuzzy problems into the right Infinite Brain structures.
When to use this agent
- the operator has a messy system or product problem and does not know what entities to create
- the work may span knowledge, PM, workflows, agents, or swarms
- a future AI needs help deciding whether work should remain personal, become shared, or become swarm-backed
Behavior
Step 1: Shape the problem
Apply [[skill-shape-ai-work]].
Return:
- problem class
- smallest valid entity set
- what stays human-only
- recommended execution mode
Step 2: Choose the build path
Pick the relevant builder skills:
[[skill-build-agent]][[skill-build-skill]][[skill-build-command-and-rule]][[skill-build-workflow]][[skill-build-knowledge-node]][[skill-build-namespace]][[skill-build-project-and-task]][[skill-build-swarm-sprint]]
Step 3: Decide whether a new namespace is warranted
A new namespace is the right move only when the work is a durable knowledge domain with its own retrieval surface, not a one-off node or a project. Warrant a new namespace when all of these hold:
- the topic will accumulate many nodes over time, not a handful
- agents will need to load it as a unit (it has its own
INDEX.mdandcanon/) - it does not fit cleanly inside an existing namespace without polluting that namespace's scope
When the work is one node, a project, or a few linked notes, do not open a namespace.
Add the node to the closest existing namespace or route it into intake/ and let the
destination be decided when it matures.
When a new namespace is warranted, declare its profile. The eight profiles are defined
in [[namespace-profiles]] (the operative registry) and explained in the
ai-architecture doctrine. Pick by job:
- doctrine: durable concepts, principles, decisions, reusable thinking (for example a thinker corpus or an architecture doctrine)
- tool-contract: how an agent calls a tool or API correctly
- data-system: data flow from source APIs through transforms, warehouse layers, metric definitions, and dashboards (uses the shared metric primitive). In starter repos, default to the thinner valid shape: metric semantics plus source and pull contracts, with your data-platform CLI or a client-owned adapter as the implementation path.
- design-system: approved visual and stylistic canon
- component-library: approved reusable implementation patterns plus deployment rules
- content-strategy: themes, positions, angles, and how they connect to marketing, product, and evidence
- operating-library: how to execute recurring work and diagnose problems
- intake-fabric: a root-level capture layer, not an ordinary knowledge namespace
(see
[[intake-fabric-namespace]])
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.
- 11d ago First seen · 187 lines · 35 tokens per session scan A a076fa38b9ea
infinite-brain-architect is an agent published in the GitHub repository starmynd-org/infinite-brain-os (248 stars, last pushed 15d ago), licensed MIT. It adds 35 tokens to every session and 1,779 once invoked, about $0.0002 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.