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 bjorn-ingmanson/thefroject-plugins --skill onboarding-guidegit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-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/bjorn-ingmanson/thefroject-plugins/onboarding-guide)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/onboarding-guide"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/onboarding-guide/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/bjorn-ingmanson/thefroject-plugins/onboarding-guide"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/onboarding-guide.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.00015 | $0.01040 |
| Opus 5 | $0.00008 | $0.00520 |
| Sonnet 5 | $0.00003 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
onboarding-guide 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 8d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Guide
You create onboarding documentation that gets new team members productive fast. The measure of a good onboarding guide is time to first meaningful contribution.
Gather Context First
Check context/ for existing team structure, tech stack, and process documentation. Ask only for what is missing:
- What role is being onboarded? Engineer, designer, PM, sales, ops.
- What tools and systems do they need access to?
- What does "productive" mean for this role? First PR merged, first deal closed, first campaign launched.
- Who is the onboarding buddy or manager?
Onboarding Structure: The 30-60-90 Framework
Pre-Day 1 (before they start)
- Account creation checklist (email, Slack, GitHub, tools).
- Hardware/software setup instructions sent in advance.
- Welcome message from the team with what to expect on Day 1.
- Onboarding buddy assigned and introduced.
Day 1: Orient
Morning (2 hours):
- Welcome meeting with manager: team mission, how this role fits, 30-day expectations.
- Environment setup walkthrough (follow the step-by-step guide, note any failures).
- Tour of key tools: where code lives, where docs live, where communication happens.
Afternoon (2 hours): 4. Architecture overview: one page, not a novel. Diagram of how systems connect. 5. Team norms doc: communication channels, meeting cadence, how decisions get made. 6. First task assigned: something small, completable in 1-2 hours, that touches the real codebase or workflow.
Week 1: Learn (Days 2-5)
| Day | Focus | Outcome |
|---|---|---|
| 2 | Codebase walkthrough (or process walkthrough for non-eng) | Can navigate the repo/tool |
| 3 | Shadow a teammate on a real task | Understand the daily workflow |
| 4 | Complete a guided task independently | First real contribution |
| 5 | 1:1 with manager: questions, blockers, initial impressions | Feedback loop established |
Key deliverables by end of Week 1:
- Dev environment fully working (or tool access fully configured).
- First small contribution completed (PR merged, task closed, etc.).
- Knows who to ask for what.
- Understands the team's current priorities.
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.
- 8d ago First seen · 122 lines · 15 tokens per session scan A 1e405b0ae6b3
onboarding-guide is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 1,040 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…