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/create-pr)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/create-pr"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/create-pr/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/kumaran-is/claude-code-onboarding/create-pr"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/create-pr.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.00059 | $0.02188 |
| Opus 5.5 | $0.00024 | $0.00875 |
| Sonnet 5.5 | $0.00012 | $0.00438 |
| Haiku 4.5 | $0.00006 | $0.00219 |
Grade A, and why
create-pr 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 1mo 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Generate a pull request with embedded risk assessment.
Step 1 — Determine diff scope
# Current branch
git rev-parse --abbrev-ref HEAD
# Target branch: use $ARGUMENTS if provided, otherwise develop
TARGET=${ARGUMENTS:-develop}
# Verify target exists; fall back to main if develop doesn't exist
git show-ref --verify --quiet refs/heads/$TARGET || TARGET=main
# Commit range
git log --oneline $TARGET..HEAD
Step 2 — Run risk assessment
Gather raw data:
git diff --shortstat $TARGET..HEAD
git diff --name-status $TARGET..HEAD
git diff --name-only $TARGET..HEAD | grep -E "package\.json$|package-lock\.json|pnpm-lock\.yaml|yarn\.lock|requirements\.txt|uv\.lock|Pipfile\.lock|pom\.xml|build\.gradle|pubspec\.yaml|pubspec\.lock"
git diff --name-only $TARGET..HEAD | grep -iE "auth|login|token|jwt|crypto|secret|password|credential|permission|role|guard|interceptor|middleware|\.env|config/.*\.(yml|yaml|json)"
git diff $TARGET..HEAD
Apply the exact same scoring logic as /pr-risk — 5 dimensions, 0–10 each:
A. Size Risk
Use the higher of file-count score and line-count score.
| Score | Files changed | OR total lines changed |
|---|---|---|
| 0–2 | ≤ 5 | ≤ 100 |
| 3–4 | ≤ 10 | ≤ 300 |
| 5–6 | ≤ 20 | ≤ 600 |
| 7–8 | ≤ 40 | ≤ 1,000 |
| 9–10 | > 40 | > 1,000 |
B. Complexity Risk
Start at 0, add points per signal found in the diff (cap at 10):
| Signal in diff | Points |
|---|---|
| Public interface or API contract changed | +2 |
| Database schema or migration file added or modified | +3 |
| Auth, security, permission, or role logic changed | +3 |
| Async or concurrent code added or modified | +2 |
| New third-party integration added | +2 |
| CI/CD, Docker, or infrastructure config changed | +1 |
| Cross-cutting concern modified (logging, error handler, event bus, interceptor) | +1 |
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.
- 1mo ago First seen · 238 lines · 0 tokens per session scan A 0aec913a1ac6
create-pr is a command published in the GitHub repository kumaran-is/claude-code-onboarding (36 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 2,188 once invoked, about $0.0002 per session on Opus 5.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
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-tag
Create and push a version tag after a release PR has been merged.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.