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 agentmods add skills/srnichols/plan-forge/onboardingnpx skills add srnichols/plan-forge --skill onboardinggit clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/srnichols/plan-forge/onboarding)<a href="https://agentmods.dev/skills/srnichols/plan-forge/onboarding"><img src="https://agentmods.dev/badge/skills/srnichols/plan-forge/onboarding.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.00037 | $0.01237 |
| Opus 5 | $0.00018 | $0.00619 |
| Sonnet 5 | $0.00007 | $0.00247 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
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 2d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Onboarding Skill
Trigger
"Onboard me to this project" / "How does this codebase work?" / "New developer setup"
Steps
1. Environment Setup
Verify prerequisites and get the project running:
git --version
dotnet --version
If this step fails (dotnet not found): Install the .NET SDK from https://dot.net/download and retry.
dotnet restore
If this step fails: Check that NuGet sources are configured correctly and network access is available.
2. Verify Build & Tests
Use the forge_smith MCP tool to diagnose environment and setup health.
dotnet build
If this step fails: Read the error output — common causes are missing SDK version (check
global.json) or missing workload.
dotnet test
If both pass: Environment is ready.
3. Architecture Overview
Read and explain:
.github/copilot-instructions.md— project overview, tech stack, conventionsdocs/plans/PROJECT-PRINCIPLES.md— non-negotiable principles (if exists)- Project structure — explain the folder layout and what lives where
- Key patterns — how data flows through the layers (Controller → Service → Repository)
4. Key Files Tour
Walk through the most important .NET files:
- Entry point:
Program.cs— startup, DI registration, middleware pipeline - Configuration:
appsettings.json,appsettings.Development.json— settings per environment - Solution file:
*.sln— project structure and dependencies - Database: migrations folder, DbContext, connection configuration
- Testing: test projects, how to run specific test classes
- CI/CD: GitHub Actions workflows, Dockerfile, deployment config
5. Plan Forge Pipeline Tour
Explain how the team works:
- Plans live in
docs/plans/— each feature is a hardened phase plan - Guardrails live in
.github/instructions/— auto-load based on file type - Pipeline prompts — Step 0–5 workflow for building features
- Skills — type
/in Copilot Chat to see available automations - Reviewer agents — specialized reviewers in
.github/agents/
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.
- 2d ago First seen · 127 lines · 37 tokens per session scan A 05b413e0982d
onboarding is a skill published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,237 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-09-03.
Other skills, from other repositories
profile
/profile - Session Profile Manager.
educate
Use this agent when you need to create end-user learning materials, tutorials, glossaries, user journey maps, quick-start guides, or concept explainers for the project being built.
learn
Consolidated reference combining advanced Claude Code workflows and AI-assisted learning techniques.
ring:generating-release-guides
Generating an internal Operations-facing update/migration guide from the git diff between two refs, documenting per-change client impact, deploy ordering, monitoring, and rollback notes in English, pt-br, or both. Use when preparing a version release or recording what changed for the Ops team. Runs read-only by…
onboarding
Get a new joiner productive in their first week.
go
Project Kickstart - PRD-First Orchestrator.