Borrowing it
Nothing to install: this file belongs to smileynet/teach-me. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/smileynet/teach-me/main/.kiro/steering/visual-teaching.mdgit clone --depth 1 https://github.com/smileynet/teach-meWrote 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/instructions/smileynet/teach-me/visual-teaching)<a href="https://agentmods.dev/instructions/smileynet/teach-me/visual-teaching"><img src="https://agentmods.dev/badge/instructions/smileynet/teach-me/visual-teaching.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.1 | $0.04003 | $0.04003 |
| Opus 5 | $0.02001 | $0.02001 |
| Sonnet 5 | $0.00801 | $0.00801 |
| Haiku 4.5 | $0.00400 | $0.00400 |
Grade A, and why
teach-me visual-teaching.md 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 today.
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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Teaching Guidelines
When creating lessons with diagrams or visual aids, follow these evidence-based rules.
Core Principles (Mayer, Paivio, Sweller)
- Every visual has an instructional purpose. No decoration. If removing it wouldn't hurt understanding, remove it. (Coherence principle, d=0.70)
- Labels go ON the diagram. Never separate a visual from its explanation. (Spatial contiguity, d=0.79)
- 5-9 elements max per diagram. Break complex systems into progressive layers. (Cognitive load theory)
- Dual code everything. Every diagram has a one-line verbal summary above it. (Dual coding, Paivio 1986)
- Consistent visual vocabulary. Same color/shape means same thing across ALL lessons. (Signaling principle, d=0.46)
- Static over animated. Animation only for inherently temporal processes. (Tversky et al., 2002)
Code Block Pedagogy
Code examples are teaching tools, not reference dumps. Every code block requires narrative framing — the prose around it earns the code's place in the lesson.
Required Framing
- Lead-in (before code): Name the problem or goal this code addresses. One sentence minimum. "We're replacing X with Y because..." or "To solve [limitation from above]..."
- Bridge (between sequential blocks): Explain what limitation or insight motivates the next version. Don't repeat what the code says — explain what drove the change.
- Connect-back (after code): Tie the implementation to the concept being taught. "This is [concept] in action" or "Notice how [mechanism] achieves [goal]."
Not every block needs all three — a single standalone example needs lead-in and connect-back. Sequential blocks building on each other need bridges between them.
Story Arc
A section with multiple code blocks tells a story. Each block should advance the narrative:
- What couldn't we do before? (motivation)
- What does this block add? (contribution)
- What can't we do yet? (sets up the next block)
The reader should feel progress through the code, not a list of alternatives dumped without context.
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.
- today First seen · 271 lines · 4,003 tokens per session scan A ad4032b8bd69
teach-me visual-teaching.md is an instructions file published in the GitHub repository smileynet/teach-me (3 stars, last pushed today), licensed MIT. It adds 4,003 tokens to every session, about $0.0200 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-06.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.