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/claims)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/claims"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/claims/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/claims"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/claims.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.00040 | $0.01351 |
| Opus 5 | $0.00020 | $0.00675 |
| Sonnet 5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
claims 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/claims — Multi-Operator Active-Claim Surface
Read surface for the multi-operator coordination log's active-claim view. No writes. The command folds the log through A2a's foldLog and projects the accepted set to the active sibling-claim shape (rule 7 isClaimActive predicate).
Per multi-operator-coc architecture §2.2 + §4.1 + §4.5: this command is the operator's window into "who claims what right now," including the F2-1 surfaced-not-eliminated residual (ADJACENT-class claim later overridden by a sibling SAME-class claim).
Usage
/claims
No arguments. The command always operates on the current repo's coordination log.
Flow
- Resolve identity via
.claude/hooks/lib/operator-id.js::resolveIdentity(cwd). Printverified_id+display_idso the operator knows which entries are theirs. - Read coordination log via filesystem Transport (
.claude/hooks/lib/transport-filesystem.js). - Fold via A2a's
foldLog(records, roster, {}). The foldedaccepted[]includes all records that passed rule 1 (sig) + rule 2 (chain) + rule 3 (fork) + per-record-type predicate. - Walk accepted for active claims — same projection logic M2 B1's
adjacency-leasecheck.js::projectActiveSiblingClaimsuses:- Filter
type === "claim". - Build a
releasedset (records oftype: "release"indexed by theircontent.claim_id) and areapedset (records oftype: "reap"indexed by theircontent.claim_idorcontent.reaped_claim_ref). - Resolve last-heartbeat-per-emitter via
accepted.filter(r => r.type === "heartbeat")for the rule-7 session-live predicate. - Skip if released, reaped, or session-expired.
- Filter
- Group by
display_id— own claims first; sibling claims grouped per operator. - Sort siblings by
granted_atDESC (most-recently-granted first). - Surface F2-1 contested claims — for each ADJACENT-class claim, check whether a LATER record exists that would have promoted to SAME against the same target (sibling claim's path/dir/workspace overlaps this claim's
target_path_or_glob). Mark ascontested: true.
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 · 85 lines · 40 tokens per session scan A 13f0f46c344e
claims 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 40 tokens to every session and 1,351 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
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.