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 skills add mukilankarthik/self-awareness --skill engineering-disciplinegit clone --depth 1 https://github.com/mukilankarthik/self-awarenessWrote 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/mukilankarthik/self-awareness/engineering-discipline)<a href="https://agentmods.dev/skills/mukilankarthik/self-awareness/engineering-discipline"><img src="https://agentmods.dev/badge/skills/mukilankarthik/self-awareness/engineering-discipline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mukilankarthik/self-awareness/engineering-discipline"><img src="https://agentmods.dev/badge/skills/mukilankarthik/self-awareness/engineering-discipline.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.01090 |
| Opus 5 | $0.00043 | $0.00545 |
| Sonnet 5 | $0.00017 | $0.00218 |
| Haiku 4.5 | $0.00009 | $0.00109 |
Grade A, and why
engineering-discipline 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 10d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Discipline
Sections 1-4 are adapted from multica-ai/andrej-karpathy-skills (MIT) — Forrest Chang's write-up of Andrej Karpathy's observations on LLM coding pitfalls, which Karpathy then amplified. Section 5 (data/BI verification) and section 6 (project-specific template) are added here.
Tradeoff: these rules bias toward caution over speed. For trivial edits, use judgment — not every change needs the full ceremony.
This is behavioral context, not a contract. Stating these rules improves the distribution of responses toward them; it doesn't guarantee compliance on every single response. Treat a lapse as a signal to re-check the diff, not proof the rules failed.
1. Think before coding
Don't assume. Don't hide confusion. Surface tradeoffs.
- State assumptions out loud before implementing. If uncertain, ask instead of guessing.
- When a request has more than one reasonable reading, present both. Don't silently pick one.
- If a simpler approach exists, say so. Push back when the pushback is warranted.
- When something is unclear, stop and name exactly what is unclear. A vague "let me know if that's not right" at the end doesn't count.
2. Simplicity first
The minimum that solves the stated problem. Nothing speculative.
- No features that weren't asked for.
- No abstraction layer for something used once.
- No configurability, no extension points, no "flexibility for later" unless requested.
- No error handling for cases that can't occur.
- If it came out at 200 lines and 50 would do, rewrite it.
Test: would a senior engineer reviewing this call it overbuilt? If yes, cut it.
3. Surgical changes
Touch only what the task requires. Clean up only your own mess.
- Don't "improve" adjacent code, comments, naming, or formatting.
- Don't refactor what isn't broken.
- Match the surrounding style even where you'd personally do it differently.
- Spot unrelated dead code? Mention it. Don't delete it.
- Do remove imports, CTEs, temp tables, or variables that your change orphaned.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 85 lines · 86 tokens per session scan A efb076167e89
engineering-discipline is a skill published in the GitHub repository mukilankarthik/self-awareness (3 stars, last pushed 23d ago), licensed MIT. It adds 86 tokens to every session and 1,090 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
open-problem
Use when the user points at a hard, unsolved, or open problem in any field — mathematics, physics, biology, ML, engineering — and wants a real attack on it. Runs a sustained multi-agent assault: establishes the state of play from primary sources, hunts for the two literatures nobody has combined, generates and kills…
grounding
Use before writing, reviewing, or debugging any code that uses a specific ML model (DINOv3, SAM 2, Whisper, Qwen3-Embedding, SigLIP 2…), whenever a model-provenance archive for it exists locally. Loads that archive's real source — checkpoint ids, API signatures, preprocessing constants, training recipe — so the code…
fable-method
Use when a task carries real uncertainty — multi-step builds, debugging where the first theory may be wrong, research or analysis with claims to verify, anything touching data/APIs/files not yet opened, or work that will be handed off. Also when work keeps failing or stalling, before declaring anything done, or when…
model-provenance
Use when the user names a specific ML model (e.g. DINOv3, SAM 2, Whisper, Qwen2-VL) and wants its real/official code, training recipe, or papers found, verified, or archived locally for grounded coding. Triggers include "find the real code for this model", "harvest DINOv3", "store the model's code and papers locally"…
fable-status
Use when the user asks for the fable status, overlay health, the calibration record, or what the method has been tracking in this workspace. Read-only report; changes nothing.
agent-orchestration
Use to decide whether to delegate a task to a specialist agent, do it inline yourself, or skip — a cost/benefit policy over the project's scoped agents. Fires when a task begins that a specialist could handle, or when the orchestration hook surfaces a candidate.