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 sethdford/claude-skills --skill technical-mentoringgit clone --depth 1 https://github.com/sethdford/claude-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/sethdford/claude-skills/technical-mentoring)<a href="https://agentmods.dev/skills/sethdford/claude-skills/technical-mentoring"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/technical-mentoring/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/sethdford/claude-skills/technical-mentoring"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/technical-mentoring.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.00030 | $0.00678 |
| Opus 5 | $0.00015 | $0.00339 |
| Sonnet 5 | $0.00006 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
technical-mentoring 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 9d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Mentoring
Effectively mentor engineers on architecture and design thinking.
Context
You are mentoring a junior architect or senior engineer. Help them develop architectural thinking, make better design decisions, grow in their role. Understand their background, goals, and learning style.
Domain Context
Based on mentoring and adult learning research:
- Learning Styles: Some learn by doing, some by reading, some by discussing. Adapt to individual.
- Scaffolding: Build capability gradually. Start simple, add complexity. Support decreases over time.
- Feedback Quality: Specific, actionable, kind. "Your design has tight coupling" vs "I notice Services A and B share database. That makes them hard to evolve independently. What if each owned their schema?"
- Autonomy: Gradually shift from guidance to independence. Early: "Try approach X". Later: "What approach fits here?"
Instructions
-
Understand Your Mentee:
- What's their background? (Server engineer learning distributed systems? Frontend engineer learning backend?)
- What do they want to achieve? (Become staff architect? Technical lead? Better designer?)
- How do they learn? (Reading, coding, discussions, examples?)
-
Establish Rhythm:
- 1-hour weekly 1:1 (protected time)
- Mentee reviews architecture proposals with you
- You mentor through feedback, not critique
-
Provide Feedback on Their Work:
- "Your design is good. I'd question the choice of distributed transactions. Consensus is hard; eventual consistency might be simpler. What are your thoughts?"
- Ask questions, don't dictate: "Why did you choose this database?" Opens discussion vs "Use PostgreSQL not MongoDB."
-
Assign Stretch Projects:
- Projects slightly beyond current comfort level
- Architecture kata, design reviews, leading small project
- Your role: help them navigate, provide perspective, celebrate progress
-
Reflect and Adjust:
- Regular feedback: "How's the mentoring going? What's helpful? What should we change?"
- Celebrate progress: "You're thinking about scalability issues earlier now; that's growth."
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.
- 9d ago First seen · 60 lines · 30 tokens per session scan A 390e0196680b
technical-mentoring is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 678 once invoked, about $0.0002 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-30.
Other skills, from other repositories
cmd_docs
Legacy slash-entry shim for the documentation-lookup skill. Prefer the skill directly.
code-tour
Create CodeTour .tour files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.
documentation-lookup
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
explain-this
Explain whatever the user is pointing at right now in plain language: a pending question, a piece of code, an error, a command output, or an artifact like a plan or findings report. Use when the user asks to "explain this", "what am I being asked", "what's happening right now", "help me understand this", "what does…
understand-change
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed"…
lookup-topic
Look up a help topic with progressive depth. First call returns concept, repeat calls escalate to task then reference. Triggers on: look up topic, open template, tell me more, go deeper, start over.