Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-pyWrote 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/start)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/start"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/start/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/start"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/start.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.00016 | $0.00956 |
| Opus 5 | $0.00008 | $0.00478 |
| Sonnet 5 | $0.00003 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
start 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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Present this orientation to the user in a warm, clear, jargon-free way. Adapt tone based on context — if they seem technical, be concise; if they seem new, take more time.
What is COC?
COC is a structured workflow where YOU direct an AI to build software. You don't need to write code. Your job is to:
- Describe what you want (in your own words, as detailed as you like)
- Make decisions when choices come up (we'll always explain the options clearly)
- Approve the plan before building starts
- Review the results to make sure they match your vision
The AI handles all the technical work — writing code, testing, security checks, and deployment.
The 6 Phases
| Step | Command | What Happens | Your Role |
|---|---|---|---|
| 1. Research | /analyze |
Study your idea — market fit, user needs, competition | Confirm we understood your vision |
| 2. Planning | /todos |
Create a complete project roadmap | Approve the plan before building starts |
| 3. Building | /implement |
Build the project one task at a time | Answer questions when choices come up |
| 4. Testing | /redteam |
Test everything from a real user's perspective | Review results |
| 5. Knowledge | /codify |
Capture what we learned for future sessions | Confirm the knowledge is accurate |
| 6. Authorization | /release |
Final COC authorization gate — readiness check before launch | Approve the release |
Plus /deploy when you're ready to ship the application after /release authorizes, and /ws anytime to check progress.
Repo type matters
/release and /deploy behave differently depending on what kind of project you're in:
- USE application repo (
.claude/VERSION::type = coc-project+deploy/deployment-config.md::type = application):/releaseis the COC authorization gate — it confirms readiness across testing, security, and knowledge capture;/deployis the application deployment mechanism (ships your app to its target environment). - BUILD / SDK package repo (
type = coc-build, e.g.,kailash-py,kailash-rs):/releaseis the SDK publishing command — it bumps versions, tags, and publishes to PyPI / crates.io;/deployis not applicable.
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.
- 9d ago First seen · 66 lines · 16 tokens per session scan A e0b0812eb639
start is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 24d ago), licensed Apache-2.0. It adds 16 tokens to every session and 956 once invoked, about $0.0001 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
adoption-sandbox
Entorno seguro de práctica — experimentar con Savia sin miedo a errores.
adoption-plan
Plan personalizado de adopción de Savia por rol — qué aprender, en qué orden.
hatch3r-onboard
Generate a comprehensive onboarding guide for a new developer joining the project -- spawn parallel researchers to analyze codebase structure, architecture, and conventions, then produce a tailored onboarding document with setup instructions, architecture walkthrough, coding conventions, key workflows, tribal…
gsd:help
Show available GSD commands and usage guide.
adoption-assess
Evaluar madurez de adopción de IA del equipo usando modelo ADKAR.
train-executor
Generate an executor onboarding playbook from a person's Freedom Path DELEGATE bucket. Produces SOPs in the person's voice, a training curriculum, and outdated-material flags. Non-technical-friendly — designed for Claude Desktop + Cowork usage.