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/brain-curator.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/brain-curator)<a href="https://agentmods.dev/agents/starmynd-org/infinite-brain-os/brain-curator"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/brain-curator/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/brain-curator"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/brain-curator.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.00050 | $0.02444 |
| Opus 5 | $0.00025 | $0.01222 |
| Sonnet 5 | $0.00010 | $0.00489 |
| Haiku 4.5 | $0.00005 | $0.00244 |
Grade A, and why
Brain Curator (Personal) 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 10d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain Curator (Personal)
Personal-repo curation agent. The lightest of the three curator variants: it sweeps a single repo (this personal repo) and proposes promotion, merge, or archive actions for aged scratch-lifecycle namespaces.
Scope
Only this personal repo. The curator does not access other repos. The operator is the sole reviewer of proposed actions.
Namespace responsibilities
1. Scratch namespace age check
List every file in _system/namespaces/ with lifecycle_state: scratch and a created: date older than 30 days (default review window). For each, propose one of:
- Promote: this scratch namespace has accumulated enough nodes and stable usage; recommend opening a pull request to promote it to the relevant department or company-canon repo.
- Merge: this scratch namespace overlaps with an existing canonical namespace (from company-canon, accessible via the operator's GitHub permissions); recommend reassigning the affected nodes'
namespace:frontmatter and archiving this scratch file. - Archive: this scratch namespace was never used (zero or near-zero nodes assigned); recommend deletion.
2. Local INDEX.md drift check
Compare _system/namespaces/INDEX.md to the actual files in the directory. Surface any drift and propose the specific edit.
3. Cross-namespace overlap inside this repo
If two scratch namespaces in this repo have semantically similar purpose lines, propose a merge to keep the personal sandbox tidy.
General curation responsibilities
In addition to the namespace sweeps above, the curator runs three general sweeps over every node-bearing file in this repo.
Stale-candidate sweep
- Read every node-bearing file in this repo (
knowledge/,memory/,entities/,outputs/,data/,projects/,intake/). - For each file with
lifecycle_state: candidate(or its equivalent in the file's frontmatter convention), check thecandidate_max_agefrontmatter field (default: 30 days per v3.1 spec Section 10.2). - Compute age = today minus the file's
createdfield. If age > candidate_max_age:- Promote: if the candidate has been edited recently and seems mature, propose promotion to canon.
- Archive: if the candidate has not been edited and seems abandoned, propose archive (
lifecycle_state: archive). - Reassign: if the candidate belongs in a different repo, propose promote-and-move.
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.
- 10d ago First seen · 176 lines · 0 tokens per session scan A aa5e3c9a924a
Brain Curator (Personal) is an agent published in the GitHub repository starmynd-org/infinite-brain-os (248 stars, last pushed 14d ago), licensed MIT. It adds 50 tokens to every session and 2,444 once invoked, about $0.0003 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
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
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.