whoami

whoami is a command for Claude Code from terrene-foundation/kailash-coc-claude-py. It costs 44 tokens per session (4,767 once invoked), scanned A, original, Apache-2.0.

A command that shows the current operator identity in a multi-person development setup, or registers an operator through a controlled process. It uses signing keys and a project roster to verify who is working.

In plain words
What is it for?
Use it to inspect the active operator, verify registration and role information, or run the supported registration and ownership ceremonies.
Why use it?
It makes authorship and permission levels visible when several people or agents share a repository.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

Good fit Use it to inspect the active operator, verify registration and role information, or run the supported registration and ownership ceremonies.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/terrene-foundation/kailash-coc-claude-py/whoami
Install

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.

Clone the repo
git clone --depth 1 https://github.com/terrene-foundation/kailash-coc-claude-py

Made for: Claude Code.

Wrote 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.

agentmods badge for whoami

README.md
[![agentmods](https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/whoami/github.svg)](https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/whoami)
Your own site
<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.

agentmods 80×15 button for whoami

Your own site · 80×15
<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>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,767 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash a7ef00820275, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

.claude/commands/whoami.md · 153 lines

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 from repo_floor + per-operator state (architecture §6.1); on a fresh repo defaults to L5_DELEGATED.
  • Un-rostered key (signing key configured but not in operators.roster.json)display_id and person_id print as (unregistered), verified_id shows the live fingerprint, posture: L2_SUPERVISED, plus next: /whoami --register (architecture §6.1 block-into).
  • No signing key configuredverified_id: (no signing key), posture: L2_SUPERVISED, next: configure signing key, then run /whoami --register. (The L2_SUPERVISED next: 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:

  1. 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_rolehuman (interactive workstation) or ci (deploy-key on a runner).
    • signing-key typessh (default) or gpg.
    • signing-key fingerprint — for SSH, the output of ssh-keygen -lf <pubkey> (the SHA256:… form); for GPG, the 40-hex long fingerprint from gpg --list-keys --with-colons.
    • signing-key pubkey — the armored public key body (the full ssh-ed25519 AAAA… line for SSH, or the -----BEGIN PGP PUBLIC KEY BLOCK----- block for GPG).

Read the full file on GitHub · 153 lines

Changes

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.

  1. 9d ago First seen · 153 lines · 44 tokens per session scan A a7ef00820275

Subscribe to this mod's changes

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.