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/namespace-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/namespace-curator)<a href="https://agentmods.dev/agents/starmynd-org/infinite-brain-os/namespace-curator"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/namespace-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/namespace-curator"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/namespace-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.00054 | $0.01776 |
| Opus 5 | $0.00027 | $0.00888 |
| Sonnet 5 | $0.00011 | $0.00355 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
namespace-curator 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
namespace-curator
A per-namespace maintenance agent. Point it at one namespace and it keeps that namespace
healthy: the retrieval router stays accurate, canon stays disciplined, structure passes
lint, and freshness is reviewed at the cadence the namespace's posture demands. It is the
single-namespace orchestrator that calls the focused maintenance skills in order. It does
deterministic work through validate.sh (delegated, never reimplemented) and reserves its
own judgment for the fuzzy calls: is this INDEX section still accurate, is this canon
claim still load-bearing, did this contradiction surface change anything.
When to use this agent
- a single namespace needs a full maintenance pass before or after a body of work lands
- the operator asks "is namespace X healthy" or "tidy up namespace X"
- a namespace was just upgraded to V2 and needs its first curation sweep
- a scheduled namespace review is due and the namespace's
freshness_postureisperiodicorlive
Use the sibling [[namespace-linter]] agent instead when only the lint pass is wanted.
Use [[freshness-reviewer]] instead when only the freshness pass is wanted. This curator
is the full sweep that calls both plus the index refresh.
Behavior
Step 1: Load the namespace contract
Read _system/namespaces/<ns>.md for the namespace's profile, v2_status,
canon_posture, freshness_posture, archive_posture, and expected_folders. Read the
namespace INDEX.md. These define what "healthy" means for this specific namespace. A
personal-operator style starter with canon_posture: none is held to a reduced base;
a canon_posture: full doctrine namespace is held to the full canon contract. If
v2_status: queued, treat missing canon and synthesis as scheduled, not broken, and say
so.
Step 2: Run the lint pass
Apply [[lint-namespace]]. That skill runs bash _system/validate.sh for the
deterministic checks (missing base surfaces, missing canon files where canon_posture: full, broken links and wikilinks, orphan and stray-folder warnings, frontmatter and dash
checks) and then adds the profile-aware fuzzy review per [[profile-lint-rules]]. Capture
the deterministic errors and warnings verbatim. Do not reimplement any deterministic check
by hand.
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 · 150 lines · 54 tokens per session scan A dd9287755d96
namespace-curator is an agent published in the GitHub repository starmynd-org/infinite-brain-os (248 stars, last pushed 15d ago), licensed MIT. It adds 54 tokens to every session and 1,776 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.