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/techtrailhead/devrelskills/technical-tutorialnpx skills add techtrailhead/devrelskills --skill technical-tutorialgit clone --depth 1 https://github.com/techtrailhead/devrelskillsWhat 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 | $0.00058 | $0.01769 |
| Opus 5 | $0.00029 | $0.00885 |
| Sonnet 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 yesterday.
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.
- yesterday 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 6mo ago), licensed MIT. It adds 58 tokens to every session and 1,769 once invoked, about $0.0003 per session on Opus 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
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.