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 jeremylongworth-source/AgentSkills --skill developer-onboardinggit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/developer-onboarding)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/developer-onboarding"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/developer-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/jeremylongworth-source/agentskills/developer-onboarding"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/developer-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.00047 | $0.00279 |
| Opus 5.5 | $0.00019 | $0.00112 |
| Sonnet 5.5 | $0.00009 | $0.00056 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
developer-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 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.
What it actually says
Developer Onboarding
Core Workflow
- Identify the target developer, prerequisites, platform assumptions, and first useful task.
- Read existing setup scripts, package files, docs, tests, and repo structure.
- Document setup, verification, common workflows, project layout, contribution path, and troubleshooting links.
- Keep commands copyable and scoped by operating system or host when they differ.
- Include validation checks so the user knows setup succeeded.
- Flag missing automation, stale commands, or unclear ownership.
Safety Rules
- Do not invent setup commands or environment variables.
- Do not include secrets or private service credentials in docs.
- Do not make one vendor or host mandatory when the repo supports alternatives.
Deliverable Shape
For onboarding docs, provide:
- Audience and prerequisites
- Setup steps
- Verification checks
- Repository map
- Common workflows
- Contribution path
- Troubleshooting notes
- Open gaps
References
- Read
references/developer-onboarding-checklist.mdwhen writing or reviewing onboarding docs.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 44 lines · 47 tokens per session scan A 4ebc494b72fd
developer-onboarding is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 47 tokens to every session and 279 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 skills, from other repositories
understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase.
personal-tutor
Create and continue durable Tutor Kit textbooks, lessons, practice, quizzes, review, and runnable exercises for people who want to learn or study a subject.
shikhu-study
Tutor the user through a source file with a cached summary, a guided walkthrough, and free-form Q&A — then persist a review record so future quizzes know what was covered.
explain
Explain jig vocabulary and artifacts in plain language. Three modes: term mode defines one lexicon term; artifact mode walks through a spec or ADR and its linked references; passage mode explains pasted jig output. Output is ephemeral (chat-only). Auto-triggers when you say explain this term, walk me through this…
kelly-homework-coach
A child-friendly homework coaching desk for elementary students. It explains photographed or pasted questions, studies wrong answers, keeps a mistake notebook, and prepares practice papers for review.
paper-share-html
Create or revise audience-ready HTML paper presentations for lab meetings and journal clubs. Use when Codex needs source-grounded figures and tables, a fluent live-talk narrative, verified quotations, varied explanatory diagrams, presenter-paced reveals, or browser QA for evidence fidelity, interaction, responsive…