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/whoami)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/whoami"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/whoami/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/whoami"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/whoami.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.00044 | $0.04767 |
| Opus 5 | $0.00022 | $0.02384 |
| Sonnet 5 | $0.00009 | $0.00953 |
| Haiku 4.5 | $0.00004 | $0.00477 |
Grade A, and why
whoami 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/whoami — Multi-Operator Identity
The identity-surface command for multi-operator COC ((loom-internal reference) §2.1 + §2.3). The --register, --enroll-genesis, --owner-add, --owner-depart ceremonies and the no-args read-only display all shipped under M0.
Subcommands
/whoami (no args) — print identity
Resolves the active operator via resolveIdentity(cwd) in .claude/hooks/lib/operator-id.js (architecture §2.1): signing-key fingerprint → roster persons[] lookup → identity tuple. A hint-only cache at .claude/operator-id (gitignored, per-clone) is re-derived on absence / corruption / fingerprint mismatch — tampering is harmless.
Three output shapes; each line is <field>: <value>:
- Rostered key — prints
display_id,person_id,verified_id,role,host_role,posture. Posture is the operative result the C1 gate composes fromrepo_floor+ per-operator state (architecture §6.1); on a fresh repo defaults toL5_DELEGATED. - Un-rostered key (signing key configured but not in
operators.roster.json) —display_idandperson_idprint as(unregistered),verified_idshows the live fingerprint,posture: L2_SUPERVISED, plusnext: /whoami --register(architecture §6.1 block-into). - No signing key configured —
verified_id: (no signing key),posture: L2_SUPERVISED,next: configure signing key, then run /whoami --register. (The L2_SUPERVISEDnext:pointer is advisory display; gate-side block-into enforcement is C1's job, not this command's.)
/whoami --register — propose a new person_id (PR-only)
Appends a new person_id entry to .claude/operators.roster.json via a feature-branch PR. NEVER writes directly to main — branch protection on operators.roster.json enforces the PR flow (architecture §2.3 + §6.4).
The flow:
- Collect inputs (interactive prompts to the operator):
display_id— advisory human-readable handle (e.g.bob,bob-laptop).github_login— the operator's GitHub collaborator login.host_role—human(interactive workstation) orci(deploy-key on a runner).- signing-key
type—ssh(default) orgpg. - signing-key
fingerprint— for SSH, the output ofssh-keygen -lf <pubkey>(theSHA256:…form); for GPG, the 40-hex long fingerprint fromgpg --list-keys --with-colons. - signing-key
pubkey— the armored public key body (the fullssh-ed25519 AAAA…line for SSH, or the-----BEGIN PGP PUBLIC KEY BLOCK-----block for GPG).
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 · 153 lines · 44 tokens per session scan A a7ef00820275
whoami 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 44 tokens to every session and 4,767 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.