Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-pynpx agentmods add commands/terrene-foundation/kailash-coc-claude-py/clean-instantiateWrote 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/terrene-foundation/kailash-coc-claude-py/clean-instantiate)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/clean-instantiate"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/clean-instantiate/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/commands/terrene-foundation/kailash-coc-claude-py/clean-instantiate"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/clean-instantiate.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.00036 | $0.01612 |
| Opus 5 | $0.00018 | $0.00806 |
| Sonnet 5 | $0.00007 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
clean-instantiate 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/clean-instantiate — Strip Canon Identity From A Client Clone (once, before /ecosystem-init)
When a client clones, copies, or templates canon (loom + builds + use-templates) from GitHub to
instantiate their own ecosystem, the clone inherits canon's committed coordination-substrate
identity — the genesis trust-root, the operator roster (signing keys, owner identity), the journal,
the team-memory facts, the ecosystem registry, the tenant denylist. /ecosystem-init does NOT clear
these — it presumes the client owner is already enrolled. This command is the clear-then-bootstrap
step that runs FIRST, on the client clone (canon is never touched).
It is the fourth onboarding surface, strictly BEFORE the other three: /clean-instantiate (once,
on a fresh client clone) → /ecosystem-init (once per fork — re-anchors genesis to YOUR owner) →
/enroll (once per operator) → /onboard (read-only, every session).
Usage: /clean-instantiate — runs in the current clone's checkout.
Procedure depth (the contamination-surface map, the assert-zero gate semantics, troubleshooting a
fail-closed residual) lives in .claude/skills/46-clean-instantiate/SKILL.md per cc-artifacts.md
Rule 3; this command is the entry point. The engine is .claude/bin/clean-instantiate.mjs; the
"what counts as canon identity" judgement is the SHARED .claude/bin/lib/identity-scrub.mjs lib —
the exact gate the public-fork publish fence uses, so the two fences cannot drift.
What it clears (plain language)
- Operator roster → reset to a placeholder. Canon's owner identity, signing keys, and trust-root
are removed; YOUR
/ecosystem-init+/enrollre-establish them. - Decision journal (
journal/) → deleted. Canon's recorded decisions are canon's, not yours. - Team-memory facts → cleared (the index README is kept).
- Ecosystem registry (
ecosystem.json) → reset to a placeholder, withupstream_canonpointed at the canon you cloned from (so your fork is recognised as a fork; the cross-ecosystem write-fence's operative activation stays gated on #576 — the entry-point hook is registered at F3 Level-1). - Tenant denylist → emptied.
- Per-clone coordination state (logs, posture, lease, init markers) → cleared if a copy carried them.
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.
- 7d ago First seen · 108 lines · 36 tokens per session scan A 8e8151060e6f
clean-instantiate is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 23d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,612 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-09-03.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.