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 jnMetaCode/skillet --skill repo-onboardinggit clone --depth 1 https://github.com/jnMetaCode/skilletWrote 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/jnmetacode/skillet/repo-onboarding)<a href="https://agentmods.dev/skills/jnmetacode/skillet/repo-onboarding"><img src="https://agentmods.dev/badge/skills/jnmetacode/skillet/repo-onboarding/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/jnmetacode/skillet/repo-onboarding"><img src="https://agentmods.dev/badge/skills/jnmetacode/skillet/repo-onboarding.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.00048 | $0.00613 |
| Opus 5 | $0.00024 | $0.00307 |
| Sonnet 5 | $0.00010 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
repo-onboarding 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 10d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-onboarding
Resist editing until you can answer: how do I run it, how do I test it, where does the change go, and what style does this house write in?
Procedure (15 minutes, in order)
- The README + manifest first.
README.md, then the manifest (package.json/pyproject.toml/go.mod/Cargo.toml): name, scripts, dependencies. Thescriptsblock is the repo telling you its verbs. - Find the entry points.
bin/mainfields,src/index.*,cmd/,__main__.py. Trace one request/command end-to-end at skim depth — names only, no line-reading. - Establish the test loop before touching anything. Run the test command; record how long it takes and whether it's green at HEAD. A red baseline changes everything you conclude later.
- Map the directories (one line each, only top two levels). Mark the ones that are generated/vendored so you never read them again.
- Sample the house style. Open the 2–3 most-recently-changed source files
(
git log --name-only -10): error handling pattern, naming, comment density, test structure. Your changes should be indistinguishable from these. - Find the seams. Where does config enter? Where is I/O isolated? What is the one module everything imports? That module is load-bearing — changes there need the most care.
- Check the repo's own rules:
CONTRIBUTING.md,CLAUDE.md,.github/workflows (what CI actually enforces), lint configs.
Output
Write a short map (10–20 lines) before starting the actual task:
run: npm start (src/cli.js) test: npm test, ~6s, green at HEAD
flow: cli.js → commands/* → store.js (all persistence) → index.json
style: ESM, no deps, errors thrown as plain Error, tests in test/*.test.js
care: store.js is imported everywhere; schema changes ripple
rules: CI runs lint+test on 3 OS; commits are conventional
Keep it honest — list what you didn't look at, so later-you knows where the map has blank spots.
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.
- 10d ago First seen · 50 lines · 48 tokens per session scan A 121c37ee7847
repo-onboarding is a skill published in the GitHub repository jnMetaCode/skillet (1 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 613 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-08-31.
Other skills, from other repositories
context-builder
Gather comprehensive project context before starting implementation. Use at the beginning of complex tasks to understand codebase structure, dependencies, patterns, and conventions before writing code.
project-map
Generates a compact structural orientation document (.agentic/project-map.md) so any agent can understand codebase structure without filesystem exploration. Invoked when onboarding to a codebase, exploring unfamiliar projects, or auditing code layout and conventions.
repository-discovery
Use this skill to systematically explore an unfamiliar codebase before making any changes. Activates when starting work in an unknown repository, adding a new feature, debugging without prior context, or when no CONTEXT.md exists. Produces a grounded understanding of architecture, conventions, and constraints.
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
scope-appropriate-architecture
Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering. Use when designing architecture, selecting patterns, or detecting a project tier.
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…