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/wrapup)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/wrapup"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/wrapup/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/wrapup"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/wrapup.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.00020 | $0.03829 |
| Opus 5 | $0.00010 | $0.01914 |
| Sonnet 5 | $0.00004 | $0.00766 |
| Haiku 4.5 | $0.00002 | $0.00383 |
Grade A, and why
wrapup 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The only deliverable is a .session-notes file that lets a fresh session start producing work within 2–3 minutes of reading it, without having to re-explore the codebase.
Before running: if significant decisions, discoveries, or risks from this session are not yet in journal/, run /journal new DECISION|DISCOVERY|RISK <topic> first. .session-notes is not a decision log.
Release drift check (MUST — BUILD repos only): Before writing .session-notes, run node .claude/hooks/lib/release-drift.js via a quick inline check (or inspect the [RELEASE-DRIFT] lines from session-start). If any packages have commits since their last tag, surface this to the user with a recommendation to run /release before ending the session. Record the unreleased package list in .session-notes under an "Unreleased packages" section so the next session sees the backlog. Silent on downstream repos / non-package repos.
What the next session already has for free
Do NOT duplicate — the next session reads these directly: commits & diffs (git log / status / diff), outstanding work (workspaces/<project>/todos/active/), decisions & discoveries (workspaces/<project>/journal/), phase outputs (01-analysis/ … 04-validate/), domain specs (specs/), project context (CLAUDE.md). Per-surface detail: skills/wrapup/SKILL.md § 1.
What ONLY wrapup can provide
Four things nothing else captures:
- Priority ordering — out of everything in the repo, which files should the next session read first, and in what order
- In-flight state — what's true RIGHT NOW that isn't yet committed, journaled, or filed as a todo
- Traps — specific pitfalls the next session will walk into without warning
- Outstanding ledger (forest) — the durable, cumulative forest-vs-trees record. Per
rules/value-prioritization.mdMUST-1+2: a running ledger of every forest-level outstanding workstream / blocked-item, reconciled at EVERY wrapup (grows on add, shrinks on close). This SUBSUMES the old one-shot forest-vs-trees reasoning: instead of re-deriving bearings from memory each session, the ledger IS the bearings — carried forward verbatim, closed only with a durable receipt. See § Outstanding ledger reconciliation.
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 · 168 lines · 20 tokens per session scan A d0779969b6a3
wrapup 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 20 tokens to every session and 3,829 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
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
fire-todos
Capture, list, and manage todos during work sessions.
gsd:resume-work
Resume work from previous session with full context restoration.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
standup
A command that creates a daily stand-up report by summarizing recent work, planned tasks, calendar events, and blockers.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.