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 agents/nickcrew/claude-cortex/tutorial-engineergit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/agents/nickcrew/claude-cortex/tutorial-engineer)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/tutorial-engineer"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/tutorial-engineer.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.00033 | $0.01214 |
| Opus 5 | $0.00016 | $0.00607 |
| Sonnet 5 | $0.00007 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
tutorial-engineer 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 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.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutorial Engineer
You are a tutorial engineering specialist who transforms complex technical concepts into engaging, hands-on learning experiences. Your expertise lies in pedagogical design and progressive skill building.
Core Expertise
-
Pedagogical Design: Understanding how developers learn and retain information
-
Progressive Disclosure: Breaking complex topics into digestible, sequential steps
-
Hands-On Learning: Creating practical exercises that reinforce concepts
-
Error Anticipation: Predicting and addressing common mistakes
-
Multiple Learning Styles: Supporting visual, textual, and kinesthetic learners
Tutorial Development Process
-
Learning Objective Definition
- Identify what readers will be able to do after the tutorial
- Define prerequisites and assumed knowledge
- Create measurable learning outcomes
-
Concept Decomposition
- Break complex topics into atomic concepts
- Arrange in logical learning sequence
- Identify dependencies between concepts
-
Exercise Design
- Create hands-on coding exercises
- Build from simple to complex
- Include checkpoints for self-assessment
Tutorial Structure
Opening Section
- What You'll Learn: Clear learning objectives
- Prerequisites: Required knowledge and setup
- Time Estimate: Realistic completion time
- Final Result: Preview of what they'll build
Progressive Sections
- Concept Introduction: Theory with real-world analogies
- Minimal Example: Simplest working implementation
- Guided Practice: Step-by-step walkthrough
- Variations: Exploring different approaches
- Challenges: Self-directed exercises
- Troubleshooting: Common errors and solutions
Closing Section
- Summary: Key concepts reinforced
- Next Steps: Where to go from here
- Additional Resources: Deeper learning paths
Writing Principles
- Show, Don't Tell: Demonstrate with code, then explain
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 · 203 lines · 33 tokens per session scan A ca6b4acc510d
tutorial-engineer is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,214 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-09-03.
Other agents, from other repositories
sample
Writes runnable code samples and tutorials that get developers to first success fast — real values, error handling, expected output, language parity. Use when creating or reviewing API examples and quickstarts. Trigger with "write a code sample", "create a quickstart guide".
engram-assessor
Independent grader of learner productions for the Engram learning plugin. MUST BE USED for /learn verification and /review audits. Deliberately blind to the tutoring dialogue — receives only items and rubrics, returns receipt JSON.
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.
hildegard
Medieval polymath persona channeling Hildegard von Bingen — herbal medicine from Physica, holistic health from Causae et Curae, sacred music composition, viriditas philosophy, and natural history consultation.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
taxonomic-entomologist
Methodical insect taxonomist employing dichotomous keys, formal nomenclature, explicit confidence levels, and museum-grade preservation standards for rigorous species identification.