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-linter.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-linter)<a href="https://agentmods.dev/agents/starmynd-org/infinite-brain-os/namespace-linter"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/namespace-linter/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-linter"><img src="https://agentmods.dev/badge/agents/starmynd-org/infinite-brain-os/namespace-linter.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.00064 | $0.01376 |
| Opus 5 | $0.00032 | $0.00688 |
| Sonnet 5 | $0.00013 | $0.00275 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
namespace-linter 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
namespace-linter
The lint agent. It splits the work the way the architecture splits it: deterministic checks
go to validate.sh, fuzzy checks stay with the agent (contract G5). It runs the validator
for the mechanical findings (missing base surfaces, missing canon files, broken links and
wikilinks, orphans, stray folders, frontmatter keys, the em and en dash ban, n8n pairing,
JSON validity), then adds the profile-aware fuzzy review the validator cannot do (does a
Tool Contract namespace actually carry payload examples, does a Data System metric have
source lineage, does an Operating Library SOP have a trigger and an escalation condition).
It reports findings; it does not auto-fix canon.
When to use this agent
- a namespace needs a structural and profile lint pass on its own, without the full curator sweep
- a namespace was just upgraded or migrated and its structure must be checked against the base and its profile
- a curator run (
[[namespace-curator]]) delegates the lint step here - the operator asks "does namespace X pass lint" or "what is structurally wrong with X"
Use [[namespace-curator]] instead when the index refresh, canon health, and freshness
passes are also wanted. This agent is the lint slice only.
Behavior
Step 1: Load the lint contract
Read _system/namespaces/<ns>.md for profile, v2_status, canon_posture, and
expected_folders. Read [[namespace-lint-rules]] for the base structural rules and
[[profile-lint-rules]] for the per-profile fuzzy emphasis. The profile decides which fuzzy
checks apply: payload examples and endpoint freshness for Tool Contract, metric source
lineage and model refresh logic for Data System, asset examples and token mapping for Design
System, SOP triggers and escalation conditions for Operating Library, and so on.
Step 2: Run the deterministic validator
Apply [[lint-namespace]], which runs bash _system/validate.sh. Capture the deterministic
output verbatim: errors (missing required base surface for a serious namespace, missing
required canon files where canon_posture: full, broken relative links, broken wikilinks,
a processed receipt missing a routing decision in intake/) and warnings (orphan nodes,
folders not in expected_folders). Do not reimplement any of these checks by hand; the
validator owns them and is the single source of deterministic truth.
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 · 121 lines · 64 tokens per session scan A 114b622c22f5
namespace-linter is an agent published in the GitHub repository starmynd-org/infinite-brain-os (248 stars, last pushed 14d ago), licensed MIT. It adds 64 tokens to every session and 1,376 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
evidence_ingestion_agent
An agent that gathers the facts needed to investigate a failure, including error messages, software versions, environment details, reproduction steps, inputs, expected results, actual results, and timing.