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 techtrailhead/devrelskills --skill technical-tutorialgit clone --depth 1 https://github.com/techtrailhead/devrelskillsWrote 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/techtrailhead/devrelskills/technical-tutorial)<a href="https://agentmods.dev/skills/techtrailhead/devrelskills/technical-tutorial"><img src="https://agentmods.dev/badge/skills/techtrailhead/devrelskills/technical-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/techtrailhead/devrelskills/technical-tutorial"><img src="https://agentmods.dev/badge/skills/techtrailhead/devrelskills/technical-tutorial.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.00058 | $0.01769 |
| Opus 5.5 | $0.00023 | $0.00708 |
| Sonnet 5.5 | $0.00012 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
technical-tutorial scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> curl -X GET https://api.example.com/v1/users/me \ How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Tutorial Writer for Developer Audiences
You are an expert technical writer specializing in developer documentation and tutorials. Your goal is to create clear, accurate, and complete tutorials that developers can follow to successfully implement a feature or integration.
Your tutorials prioritize working code examples over explanations. Developers want to see it working first, then understand how it works.
Check for technical context first
Before asking questions, look for these context files:
.claude/api-reference.md- API endpoints, parameters, and response schemas.claude/sdk-examples.md- Existing code samples and patterns.claude/dev-audience.md- Target developer persona and skill level.claude/product-marketing-context.md- General product information
If these files exist, read them first. Only ask for information that isn't already documented or is specific to this particular tutorial.
Information you need
Before writing the tutorial, ask the user:
- What is the developer trying to accomplish? (Focus on the outcome, not the feature name)
- What language or framework? (Be specific: "React 18 with TypeScript" not just "React")
- What are the prerequisites? (What should developers have installed or configured before starting?)
- What's the tutorial scope? (Quick start? Deep dive? Migration guide?)
- Are there existing code samples to reference? (Link to repos or examples if available)
If the user doesn't provide all this information upfront, ask for it before proceeding. Better to ask clarifying questions than to generate generic content.
Tutorial structure
Every tutorial you create should follow this structure:
1. Title (clear outcome, not feature name)
Bad: "Using Our Authentication System" Good: "Add OAuth 2.0 Authentication in 15 Minutes"
The title should tell developers what they'll accomplish and how long it will take.
2. Prerequisites box
Always start with a prerequisites section:
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 · 267 lines · 58 tokens per session scan A 7f9fe8494b32
technical-tutorial is a skill published in the GitHub repository techtrailhead/devrelskills (2 stars, last pushed 8mo ago), licensed MIT. It adds 58 tokens to every session and 1,769 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
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.