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/commands/create-namespace.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/commands/starmynd-org/infinite-brain-os/create-namespace)<a href="https://agentmods.dev/commands/starmynd-org/infinite-brain-os/create-namespace"><img src="https://agentmods.dev/badge/commands/starmynd-org/infinite-brain-os/create-namespace.svg" alt="Measured on agentmods" 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.00000 | $0.01350 |
| Opus 5 | $0.00000 | $0.00675 |
| Sonnet 5 | $0.00000 | $0.00270 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
create-namespace 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 8d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-namespace
Create a new namespace file in _system/namespaces/ with lifecycle_state: scratch. Used in personal repos to introduce an ad-hoc namespace for a research session, project area, or governance bucket.
When to use this
- Starting a new research session that does not fit
research-generalor any other existing namespace. - Spinning up a project-area namespace that needs its own governance settings.
- Carving out a topic-specific namespace inside a personal repo for future promotion review.
When NOT to use this
- The need fits an existing canonical namespace. Use the existing one.
- You are in a department or company-canon repo. Open a pull request that adds the namespace file directly; do not create scratch namespaces in canon repos.
- The need is for a topic tag, source channel, or author distinction. Use frontmatter fields (
tags,source_channel,source_author) on the affected nodes instead. - You want to build a real namespace from an existing corpus or source folder. Use
/build-knowledge-base, which routes through the V2 profile, canon, synthesis, support, and validation machinery.
How it works
The command prompts the operator for four inputs:
- Namespace name (slug): kebab-case, e.g.,
research-llm-agents-2026,project-launch-q4,competitor-acme. - Purpose: a one-line statement of what this namespace covers.
- Group: one of
operations,research,product,competitive-intel,personal, or a new group documented in the answer. - Owner: the operator's handle (defaults to the personal repo owner).
The command then:
- Verifies the slug does not already exist in
_system/namespaces/(collision check). - Writes
_system/namespaces/{slug}.mdwith the required frontmatter and a stub body. - Appends a row to
_system/namespaces/INDEX.mdunder the catalog table and under the relevant by-group section. - Reports the file paths created or modified and reminds the operator to run
bash _system/validate.shif validate.sh is installed in this personal repo.
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.
- 8d ago First seen · 144 lines · 0 tokens per session scan A 2ac3f3209351
create-namespace is a command published in the GitHub repository starmynd-org/infinite-brain-os (248 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,350 tokens. 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 commands, from other repositories
nyann:doctor
Run nyann's read-only hygiene + documentation audit on the current repo. Emits the same drift sections retrofit uses, but never offers remediation or writes to the filesystem. Use this on session start, in CI, or any time you want to sanity-check a repo without risking mutations.
nyann:retrofit
Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.
nyann:branch
Create a strategy-compliant git branch. Same flow as the natural-language new-branch skill — dispatches here when users prefer explicit slash commands. Accepts positional args for purpose + slug so /nyann:branch feature login works directly without the skill having to parse phrasing.
nyann:apply
Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…
nyann:hotfix
Create the branch topology for a patch release against a previously tagged version. Ensures release/ . exists from the source tag, then creates hotfix/ off it. After this, the user commits the fix and runs /nyann:release from the hotfix branch.