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 Osipchuk/agent-skills --skill onboard-our-stackgit clone --depth 1 https://github.com/Osipchuk/agent-skillsWrote 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/osipchuk/agent-skills/onboard-our-stack)<a href="https://agentmods.dev/skills/osipchuk/agent-skills/onboard-our-stack"><img src="https://agentmods.dev/badge/skills/osipchuk/agent-skills/onboard-our-stack.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.00231 | $0.01477 |
| Opus 5 | $0.00115 | $0.00739 |
| Sonnet 5 | $0.00046 | $0.00295 |
| Haiku 4.5 | $0.00023 | $0.00148 |
Grade C, and why
onboard-our-stack scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
2. **No config -> COLD START.** Do NOT refuse, and do NOT drop into config How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
onboard-our-stack
Two jobs, one skill:
- Broad onboarding — "I'm new, help me understand this project." The reader needs a route through the system, in order.
- Targeted — "explain our scheduler." The reader needs one subsystem, on demand.
Tell them apart from the request: a named subsystem -> targeted; "new", "onboard me", "where do I start", "understand the project" -> broad.
The institutional knowledge — which files are load-bearing, in what order, and
the gotchas that live only in people's heads — is curated in
.claude/onboard/topics.yaml by a maintainer, ONCE, and committed. A newcomer
just asks; they never author it and never change code to make this skill work.
Availability ladder — the "works out of the box" guarantee
Pick the highest tier the repo supports. Never block the newcomer on setup, and never demand maintainer input from someone who came here to learn.
-
Curated config present (
.claude/onboard/topics.yamlat repo root) -> use it. Best tier: real ordering, real gotchas. See Broad / Targeted below. -
No config -> COLD START. Do NOT refuse, and do NOT drop into config authoring (that is a maintainer-only flow, below). Orient the newcomer from the repo's own authoritative sources, in this order if present: README.md, CLAUDE.md / AGENTS.md, ARCHITECTURE.md, docs/ (a product doc and a runbook if they exist), the dependency manifest (pyproject.toml / requirements.txt), and the entry point (main.py / app). Synthesize a grounded orientation, citing each file. Derive getting-started from README/RUNBOOK. Then say plainly: "This is auto-read from your repo's docs, not a curated walk — the tribal knowledge a teammate would warn you about (stale docs, landmines, why it's built this way) isn't captured yet. A maintainer can run the setup, or I can help one author it."
The line you must not cross: reading and citing the team's own docs is ALLOWED — that surfaces what's written, it is not a guess. Inventing gotchas, or asserting a file is load-bearing without evidence from a doc or the entry point's own imports, is NOT allowed. When unsure, attribute it or omit it.
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.
- 8d ago First seen · 117 lines · 231 tokens per session scan C fae9bf6072ba
onboard-our-stack is a skill published in the GitHub repository Osipchuk/agent-skills (5 stars, last pushed 28d ago), licensed MIT. It adds 231 tokens to every session and 1,477 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
printing-press-retro
Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for…
socratic-quiz
Use this when the user wants to deeply understand something through guided questioning. Trigger phrases include: "quiz me", "help me understand", "Socratic", "teach me", "walk me through with questions", "test my understanding", or when the user asks for an explanation and would benefit more from guided discovery than…
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
教程类H5-小红书小工具
A method for building offline, single-page course experiences for Xiaohongshu’s Mini Tools, which are interactive pages published inside the platform. It combines written lessons, generated illustrations, and JavaScript page switching in a constrained container.
sansheng-distill
A book and text summarizer that creates one self-contained HTML page with five sections: an overview, chapter notes, the book’s central idea, an action checklist, and questions for judging its reliability. The page includes an embedded Mermaid mind map and works offline without a web server.
lx
Codebase exploration tool that reads many files or whole directories in a single call, with per-file headers, glob include/exclude filters, function/type skeleton extraction (signatures only, no bodies), and head/tail line slicing.