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/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/status-check)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/status-check"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/status-check.svg" alt="Measured on agentmods" 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.00022 | $0.00310 |
| Opus 5 | $0.00011 | $0.00155 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
status-check 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 4d 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.
What it actually says
Status Check
Give me an honest status report. Follow these rules STRICTLY:
Format Required
## What WORKS (end-to-end, no caveats)
- [Feature]: ✅ User can [specific action]
## What's BROKEN (non-functional)
- [Feature]: ❌ [What happens] instead of [what should happen]
## What's NOT IMPLEMENTED (doesn't exist yet)
- [Feature]: 🚫 Not built
Rules
- NO PERCENTAGES - Never say "90% done" or "mostly complete"
- NO CONTRADICTIONS - If you list issues, it's BROKEN, not "works with issues"
- BINARY ONLY - Either it WORKS end-to-end or it's BROKEN
- NO HEDGING - No "almost", "nearly", "mostly", "partially"
- MATCH SUMMARY TO DETAILS - If details show problems, summary must say BROKEN
Self-Check Before Responding
Ask yourself:
- Did I say something "works" then list why it doesn't? → REWRITE
- Did I use a percentage? → REMOVE IT
- Did I use "mostly/almost/nearly"? → REPLACE with WORKS or BROKEN
$ARGUMENTS
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.
- 4d ago First seen · 39 lines · 22 tokens per session scan A 530a60952edb
status-check is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 310 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
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.