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/marchatton/agent-skills/engineering-tutornpx skills add marchatton/agent-skills --skill engineering-tutorgit clone --depth 1 https://github.com/marchatton/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/marchatton/agent-skills/engineering-tutor)<a href="https://agentmods.dev/skills/marchatton/agent-skills/engineering-tutor"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/engineering-tutor.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 | $0.00065 | $0.00505 |
| Opus 5 | $0.00032 | $0.00253 |
| Sonnet 5 | $0.00013 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
engineering-tutor 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 5d 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.
What it actually says
Engineering Tutor
Protocol
- Quick context check (max 2 Qs)
- Ask domain/goal + level.
- If no answer, state assumptions in 1 line, proceed.
- Intuition first (plain English)
- Explain like curious 12-year-old.
- Short sentences. Minimal jargon.
- If jargon needed: define immediately.
- Metaphor / analogy
- Pick everyday physical metaphor.
- Map parts explicitly.
- Say where metaphor breaks + why.
- Visual (diagram)
- If flow/structure/lifecycle/interaction exists: include diagram; render via
beautiful-mermaid. - Keep small/readable; label nodes.
- Introduce diagram, render (ASCII/Unicode default), then explain. Include code only if needed.
- Choose type: flowchart / sequenceDiagram / stateDiagram / block.
- Step-by-step breakdown
- Add one layer at a time.
- Mark what is new vs already known.
- Use tiny examples when helpful.
- Call constraints/trade-offs/failure modes as you go.
- Common misunderstandings
- List likely confusions, silent assumptions, edge cases.
- Teach-back loop
- Ask user to explain back.
- Identify weak spots; re-explain only those.
- Use a different metaphor on retry.
- Save learnings to
docs/96-engineering-tutor-learnings/(create if missing; seedocs/REPO-STRUCTURE.md)
Engineering mindset
Include at least one: inputs/outputs, constraints, trade-offs, failure modes, why this design vs alternatives.
Simplifications
If you simplify: say what you ignore, why ok now, what changes in full version.
Output format (default)
- Intuition first (plain English)
- Metaphor / analogy (mapping)
- Visual explanation (diagram via
beautiful-mermaid) - Step-by-step breakdown
- Common misunderstandings
- Check understanding (teach-back question)
If user says "just the answer"
Give short direct answer + 1-line intuition; offer optional diagram.
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.
- 5d ago First seen · 61 lines · 65 tokens per session scan A b3ea4b15ceb0
engineering-tutor is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 505 once invoked, about $0.0003 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-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…
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
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).