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 0ryant/engineering-doctrine --skill normative-language-readinggit clone --depth 1 https://github.com/0ryant/engineering-doctrineWrote 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/0ryant/engineering-doctrine/normative-language-reading)<a href="https://agentmods.dev/skills/0ryant/engineering-doctrine/normative-language-reading"><img src="https://agentmods.dev/badge/skills/0ryant/engineering-doctrine/normative-language-reading/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/0ryant/engineering-doctrine/normative-language-reading"><img src="https://agentmods.dev/badge/skills/0ryant/engineering-doctrine/normative-language-reading.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.00076 | $0.00948 |
| Opus 5.5 | $0.00030 | $0.00379 |
| Sonnet 5.5 | $0.00015 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
normative-language-reading 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Normative Language Reading Skill
Kind: always-on primer for doctrine consumers and authors Authority: advisory; the strength of a claim is set by its owning file, not by this skill
Purpose
Agents over-read and under-read normative text in predictable ways: they treat bold or imperative prose as a rule, assign one strength to a whole document, apply profile-scoped obligations universally, and turn missing evidence into a pass. This skill installs the reading discipline of normative-language-applicability-and-exceptions.md so those failures are caught at the point of reading.
Instructions
When you read or write a doctrine claim:
1. Only capitalised MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY carry BCP 14 force; CONTEXT-DEPENDENT and EXAMPLE are library content classes. Bold type, imperative tone, or a checkbox creates no obligation.
2. Read strength per claim, never per document. Report a claim as: <path> section <n>: <keyword> - <outcome preserved or failure prevented>.
3. Before applying a claim, confirm its applicability overlay: baseline, named profile, or binding external authority. A profile-scoped MUST is not universal.
4. Departure from a MUST requires a recorded exception naming the claim, the accountable authority, the compensating control, and an expiry. Departure from a SHOULD requires a recorded reason when material. Silence grants no permission.
5. Absent, failed, untrusted, or inconclusive evidence is never a pass. Say which of the four it is.
6. When two claims conflict, prefer the stricter result where both protect the same property; otherwise record the conflict for an accountable decision rather than resolving it yourself.
Run-Contract Use
context:
skills:
- [email protected]
verifiers:
- [email protected]
What ships with it
1 file 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.
- 1mo ago Changed · +1 lines 71c6d2935e2c
- 1mo ago First seen · 88 lines · 76 tokens per session scan A bc7c6c8f8ade
normative-language-reading is a skill published in the GitHub repository 0ryant/engineering-doctrine (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 948 once invoked, about $0.0003 per session on Opus 5.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-04.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…