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/code-validation-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/code-validation-teaching)<a href="https://agentmods.dev/instructions/smileynet/teach-me/code-validation-teaching"><img src="https://agentmods.dev/badge/instructions/smileynet/teach-me/code-validation-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.02028 | $0.02028 |
| Opus 5 | $0.01014 | $0.01014 |
| Sonnet 5 | $0.00406 | $0.00406 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
teach-me code-validation-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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Validation for Teaching Content
When writing lessons that include executable code, validate every code block before publishing. A learner encountering broken code loses trust in the material and conflates "I don't understand this" with "this doesn't work" — the worst possible confusion for learning.
The Validation Contract
Every lesson with code blocks MUST have:
- Final-state files at
reference/code/{lesson-slug}/— the assembled output after all diffs applied - A validation step that confirms those files are syntactically and semantically correct
- Integration with
mise run verify— validation runs automatically, not manually
Finding Validation Tools (any language)
Before writing code-based lessons for a new domain, research validation tooling:
Discovery checklist
| Question | Where to look |
|---|---|
| Does the language have a CLI compiler/interpreter? | Official docs — rustc --check, python -c, tsc --noEmit |
| Is there a standalone linter? | Package registries — eslint, clippy, flake8, golangci-lint |
| Does the editor tooling expose a CLI? | LSP servers sometimes have --check modes |
| Can the runtime validate without executing? | python -m py_compile, ruby -c, perl -c |
| Is there a type checker? | mypy, pyright, flow, tsc |
Priority order (most to least reliable)
- Official compiler/interpreter —
rustc,go build,javac,gcc. Always right. - Language-specific linter —
eslint,clippy,shellcheck. Catches more than syntax. - LSP in check mode — When no CLI exists, wrap the LSP's diagnostic endpoint.
- Type checker — For dynamic languages where the runtime won't catch mismatches.
- Runtime in headless/batch mode — When no standalone tool exists, use the actual runtime (Godot headless, Unity batch mode). This is the floor, not a fallback.
When no validator exists (the gdshader problem)
Some domain-specific languages lack CLI tooling entirely. Strategy:
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 · 129 lines · 2,028 tokens per session scan A 6ac49afbf6f6
teach-me code-validation-teaching.md is an instructions file published in the GitHub repository smileynet/teach-me (3 stars, last pushed today), licensed MIT. It adds 2,028 tokens to every session, about $0.0101 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.