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.
npx skills add terrene-foundation/kailash-coc-claude-py --skill 44-enrollgit 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/skills/terrene-foundation/kailash-coc-claude-py/44-enroll)<a href="https://agentmods.dev/skills/terrene-foundation/kailash-coc-claude-py/44-enroll"><img src="https://agentmods.dev/badge/skills/terrene-foundation/kailash-coc-claude-py/44-enroll/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/skills/terrene-foundation/kailash-coc-claude-py/44-enroll"><img src="https://agentmods.dev/badge/skills/terrene-foundation/kailash-coc-claude-py/44-enroll.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.00047 | $0.01486 |
| Opus 5 | $0.00023 | $0.00743 |
| Sonnet 5 | $0.00009 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
44-enroll 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/enroll — Operator Enrollment Procedure
The procedure backing .claude/commands/enroll.md (the once-per-operator ceremony for joining an
ecosystem already configured by /ecosystem-init). The command body holds the three load-bearing
invariants; this skill holds the step-by-step procedure and the exact tool-call shapes.
Three onboarding surfaces (rules/enrollment-operations.md): /onboard (read, every session),
/enroll (operator, once), /ecosystem-init (fork, once). They share ZERO write-authority.
Ceremony steps: B1 → B2 → B3
B1 — roster registration (wraps /whoami --register)
Invoke the EXISTING /whoami --register path (.claude/commands/whoami.md). It is the ONLY roster-write
path (multi-operator-coordination.md §1); /enroll does NOT re-implement it. The /whoami --register
flow:
- Collect inputs:
display_id(advisory handle),github_login(orprincipalEntra UPN on an ADO ecosystem),host_role(human|ci), signing-key{type: ssh|gpg, fingerprint, pubkey}. - Derive
person_id=pid-<display_id>-<short-fingerprint>(first 8 chars of sha256 of the pubkey body); immutable. - Cut a feature branch off
main:git checkout -b "codify/${display_id}-$(date -u +%Y-%m-%d)" origin/main— NEVER writeoperators.roster.jsondirectly tomain(branch protection rejects it). - Schema-validate the in-memory roster edit via
.claude/hooks/lib/roster-schema-validate.js; avalid: falseis a hard stop. - Commit + push + open PR — the PR enters the branch-protection + review chain. Merge is NEVER a direct push and NEVER an owner-self-attesting admin-merge (the §6.4 gate matrix's job).
New operators default to role: contributor. Promotion to senior/owner is a SEPARATE quorum gate
(--owner-add for owners, a 2-of-N roster edit for senior) — NOT part of /enroll.
Business-role caveat (Q1). The three business roles are the advisory business_roles enum at
operators.roster.schema.json:94-105 (platform-engineer / capability-engineer / business-consultant),
ORTHOGONAL to the authority role and NEVER quorum-eligible (multi-operator-coordination.md §1).
/enroll places the operator into an AUTHORITY role; business_roles is an additive field the operator
or an owner may set later — it never touches the display_id/verified_id/person_id authority triple.
product-owner is NOT a roster value (the brief author sits outside the delivery substrate).
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 · 90 lines · 47 tokens per session scan A bf7f70cf9521
44-enroll is a skill published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 24d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,486 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.