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/ws)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/ws"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/ws/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/ws"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/ws.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.00010 | $0.00478 |
| Opus 5 | $0.00005 | $0.00239 |
| Sonnet 5 | $0.00002 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
ws 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.
What it actually says
Display the current workspace status. Do not modify any files.
-
List all directories under
workspaces/(excludinginstructions/and_template/). -
For the most recently modified workspace (or
$ARGUMENTSif specified):- Show workspace name and path
- Derive current phase from filesystem:
- Has
01-analysis/files -> Analysis done - Has
todos/active/files -> Todos created - Has
todos/completed/files -> Implementation in progress - Has
04-validate/files -> Validation done - Agents/skills were updated in phase 05 -> Codification done (check workspace
.session-notesor04-validate/)
- Has
- Count files in
todos/active/vstodos/completed/ - List the 5 most recently modified files in the workspace
- If
.session-notesexists, show its contents and age
Missing-phase scan (loom #19 P2)
Before reporting the summary, check for missing canonical phase dirs against the contract in (loom-internal reference):
briefs/,01-analysis/,02-plans/,03-user-flows/,04-validate/,journal/,todos/active/,todos/completed/
For each missing dir, emit a flagged warning at the TOP of the output (use
!! MISSING: prefix so it's visually loud in plain terminals):
!! MISSING: briefs/ — /analyze likely skipped; ask user for a brief
!! MISSING: 01-analysis/ — architecture work without /analyze; halt and run it
!! MISSING: todos/active/ — /todos was skipped; halt and run it before /implement
Missing-phase dirs are NOT a failure — they are a signal that the corresponding phase has not run yet. The flag is advisory.
Journal
- Read the workspace's
journal/directory - Count total entries and entries by type
- Show the 3 most recent entries (number, type, date, topic)
- Present as a compact summary.
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 · 48 lines · 10 tokens per session scan A b020c737fa9f
ws 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 10 tokens to every session and 478 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.