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/fikrilal/engineering-agent-skills/tutor-codenpx skills add fikrilal/engineering-agent-skills --skill tutor-codegit clone --depth 1 https://github.com/fikrilal/engineering-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/fikrilal/engineering-agent-skills/tutor-code)<a href="https://agentmods.dev/skills/fikrilal/engineering-agent-skills/tutor-code"><img src="https://agentmods.dev/badge/skills/fikrilal/engineering-agent-skills/tutor-code.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.00071 | $0.00646 |
| Opus 5 | $0.00036 | $0.00323 |
| Sonnet 5 | $0.00014 | $0.00129 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
tutor-code 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 3d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutor Code
Teach enough language and framework knowledge for the learner to reason about real repository code. Do not turn a focused question into a generic language course.
Workflow
- Identify the exact learning target and infer the learner's known languages, frameworks, and current depth from the conversation. Ask only when the target or learner context is genuinely ambiguous.
- Read repository instructions and inspect the target in context: declarations, call sites, concrete implementations, tests, and relevant configuration.
- Explain the code's role in the product before explaining syntax.
- Walk through runtime behavior in execution order. Track important values, ownership, mutation, errors, and side effects.
- Isolate only the unfamiliar language or framework constructs needed to understand that behavior.
- Map each construct to a known concept when the structures genuinely correspond. State where the analogy breaks down.
- Explain why this implementation shape is useful here and whether it is a language requirement, framework convention, repository convention, or design choice.
- Stop once the learner can follow the requested code. Add edge cases, tests, or exercises only when requested.
Explanation Depth
Use progressive depth:
- First pass: purpose, runtime story, and only essential syntax.
- Second pass: ownership, types, framework mechanics, and design tradeoffs.
- Deep dive: compiler behavior, memory model, generated code, or advanced internals only when requested or required to answer correctly.
Investigate deeply enough to be correct, but do not front-load deep output.
Output
Default to this compact shape:
- Purpose: what responsibility this code has in the system.
- Runtime story: what happens in execution order.
- Unfamiliar parts: only the syntax or framework concepts blocking understanding, with a precise analogy where useful.
Explain why the shape matters only when it is not obvious. For a short expression, answer directly without manufacturing sections.
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.
- 3d ago First seen · 58 lines · 71 tokens per session scan A 1920603ab50a
tutor-code is a skill published in the GitHub repository fikrilal/engineering-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 646 once invoked, about $0.0004 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
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.
ljg-learn
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or…
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.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.