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 me2resh/apexyard --skill tutorialgit clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/tutorial)<a href="https://agentmods.dev/skills/me2resh/apexyard/tutorial"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/tutorial/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/me2resh/apexyard/tutorial"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/tutorial.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 83 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00042 | $0.02960 |
| Opus 5 | $0.00021 | $0.01480 |
| Sonnet 5 | $0.00008 | $0.00592 |
| Haiku 4.5 | $0.00004 | $0.00296 |
Grade B, and why
tutorial scanned grade B 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
signal=$(cat .claude/session/onboarding-tech-level 2>/dev/null || echo "") How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/tutorial — Replay the Capability Tour
This is ticket #911 (M3) of the guided-onboarding walking skeleton (technical
design: docs/technical-designs/onboarding-increment-1.md, § D3/D4 and the
"Standalone /tutorial Reusability Spec"), layered with increment 2's
depth adaptivity (ticket #914, § D2/D5/D7) and now grown by #915 (M7)
to also render the full teach-in-context glossary — US-6 in full
(technical design: docs/technical-designs/onboarding-increment-2.md § D5).
/tutorial is a standalone, read-only re-entry point to the same
capability tour /onboard shows on first run, plus the plain-language
glossary for the five core SDLC terms — for the adopter who skipped either,
missed them, or just wants to see them again without faking a fresh fork.
#914 wired /tutorial onto the shared depth-mode marker so it renders
in the adopter's current terse/guided mode (one short "why this
matters" sentence per section in guided mode; bare, byte-for-byte
unchanged rendering in terse — NFR Backward-compat). This ticket (#915)
adds the full glossary render after the tour — reading the same shared
docs/onboarding/glossary.md asset /onboard's guided-mode asides already
read one term at a time (#913) — and lifts the "tour-only" scope note from
Rule #4 below. It does not touch the depth-mode marker's derivation,
override, or transparency logic (that stays #914's, unchanged), and it does
not touch /onboard's asides or the glossary content itself (that
stays #913's).
What this skill does NOT do
/tutorial is deliberately disconnected from /onboard, /setup, and
/handover — it must work identically whether the fork is fresh, already
configured, or predates this feature entirely (US-6 AC). Concretely, it
never:
- Reads or writes
onboarding.yaml - Triggers fresh-fork detection (it does not call
fresh_fork_state()— see.claude/hooks/_lib-fresh-fork.sh— for gating; that function exists for/onboardand the SessionStart hook, not for this skill) - Runs any part of the
/setupor/handoverflows - Writes to
apexyard.projects.yamlor any other registry - Touches the active-ticket marker or the bootstrap marker
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.
- 7d ago First seen · 265 lines · 42 tokens per session scan B 6bf27dfc832b
tutorial is a skill published in the GitHub repository me2resh/apexyard (498 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 2,960 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.