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 n24q02m/claude-plugins --skill onboard-repogit clone --depth 1 https://github.com/n24q02m/claude-pluginsWrote 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/n24q02m/claude-plugins/onboard-repo)<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/onboard-repo"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/onboard-repo/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/n24q02m/claude-plugins/onboard-repo"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/onboard-repo.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.00038 | $0.01606 |
| Opus 5 | $0.00019 | $0.00803 |
| Sonnet 5 | $0.00008 | $0.00321 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
onboard-repo 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 12d 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.
This is a copy
100% identical to onboard-repo — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard Repo
Take a codebase you have never seen and turn it into a queryable graph, then read the graph to produce an orientation map. Use this on first contact with a repository, before answering questions about it or changing anything in it.
Scope: this skill builds and reads a knowledge graph. It does not modify source files, CI configuration, or project conventions. The only files it creates are the graph database under .code-review-graph/ (already self-ignored) and, when you choose to add one, a .code-review-graphignore.
Command surface: run the local CLI through the coding harness shell. Examples
use the installed better-code-review-graph command; from a source checkout,
prefix it with uv run. No MCP mapping is required.
Steps
-
Check what already exists with
better-code-review-graph graph stats --repo-root "<path>". A non-empty graph can go directly to step 5; a missing-graph error means continue with a build. -
Decide the indexing scope before building:
- Single repository: pass only
--repo-root "<path>". - A repository that vendors or embeds others: add a
.code-review-graphignoreat the repo root (onefnmatchpattern per line,#for comments) so vendored trees, build output, and fixtures do not inflate the graph. Common additions:vendor/*,third_party/*,**/generated/*,**/*.min.js. - Several sibling repositories that call each other: federate them in one graph with
--rootsin step 3, then useimpact-auditfor cross-repo questions.
- Single repository: pass only
-
Build the graph with
better-code-review-graph graph build --full-rebuild --repo-root "<path>".- For a federated build:
better-code-review-graph graph build --full-rebuild --repo-root "<path-a>" --roots "<path-b>". Each root is registered in the repo registry and its files are tagged with arepo_id, which later lets you scope any query with--repo "<repo_id>". - Parsing is Tree-sitter based and needs no language servers, toolchains, or compilation -- an unbuildable checkout still indexes.
- For a federated build:
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.
- 12d ago First seen · 103 lines · 38 tokens per session scan A 9c53ca394db2
onboard-repo is a skill published in the GitHub repository n24q02m/claude-plugins (4 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 1,606 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to onboard-repo, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
project
A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.
doc-html-slide
A renderer that turns presentation content into a single HTML slide deck that opens directly in a browser. It creates a 16:9 slide sequence with navigation, fullscreen viewing, printing to PDF, and speaker-note controls.
cs-channel-message
A channel-message writing tool for search ads, advertising, customer relationship messages, and app notifications. It uses the NCM sequence—Need, Channel, Moment, Message, and CTA—to adapt wording to where and when customers see it.
media-higgsfield-explainer
A Higgsfield workflow for making non-photorealistic narrated explainer videos. It pairs each narration line with a 10-second animated clip and joins the clips into one finished video.
finance-investor-relations
An investor-relations tool for preparing pitch decks and three-year financial models for fundraising. An IR, or investor-relations, deck explains a company to potential investors, while the model covers sales, profit, cash flow, and valuation.
career-portfolio
A portfolio-building skill for Korean job seekers that organizes projects and explains their work for development, design, marketing, and planning roles.