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 Neeeophytee/agent-stylebooks --skill w3c-technical-reportsgit clone --depth 1 https://github.com/Neeeophytee/agent-stylebooksWrote 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/neeeophytee/agent-stylebooks/w3c-technical-reports)<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/w3c-technical-reports"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/w3c-technical-reports/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/neeeophytee/agent-stylebooks/w3c-technical-reports"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/w3c-technical-reports.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.00839 |
| Opus 5 | $0.00034 | $0.00419 |
| Sonnet 5 | $0.00013 | $0.00168 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
w3c-technical-reports 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
W3C technical reports
Turn an approved technical design into a precise specification. Improve expression and structure without creating policy, consensus, conformance criteria, or requirements.
Establish authority and scope
- Identify the source of approved requirements and the decision body that owns them.
- Preserve requirement strength, actors, conditions, exceptions, algorithms, data types, error behavior, and compatibility constraints.
- Do not infer a normative requirement from an example, implementation, issue discussion, preference, or common practice.
- Mark unresolved decisions and contradictions as issues. Do not silently choose a behavior.
- State the document's scope, out-of-scope concerns, maturity, and intended implementations.
Build the conceptual model
- Identify each conformance class, implementation role, data model, and external dependency.
- Define a term before using it to carry a requirement. Use one stable term per concept.
- State how terms relate when they can be confused or overlap.
- Present the processing model in an order that exposes inputs, state changes, outputs, and errors.
- Keep implementation-specific behavior out unless the scope intentionally requires it.
Write normative requirements
- Give each requirement an identifiable actor and one testable obligation.
- Put conditions and scope next to the behavior they constrain.
- State exceptions explicitly and identify which rule they override.
- Describe observable outcomes without prescribing an implementation method unless the method is itself required for interoperability or safety.
- Keep conformance requirements in normative prose. Label examples, notes, rationale, and implementation advice as informative.
- Do not place a requirement only in a figure, table, example, or note.
Use RFC 2119 and RFC 8174 key words only when the governing document deliberately adopts
their definitions. In that case, only the uppercase forms carry the defined meanings. Do not
upgrade ordinary advice to MUST, SHOULD, or MAY; preserve the strength approved by the
specification owners. Explain a deviation from a SHOULD requirement when the source calls for it.
What ships with it
3 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 · 78 lines · 67 tokens per session scan A dd556f00ad36
w3c-technical-reports is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (59 stars, last pushed 17d ago), licensed MIT. It adds 67 tokens to every session and 839 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ciel-documentation-engine
CIEL's framework for high-integrity documentation generation, validation, and semantic indexing.
readme
Create, redesign, audit, or update a repository README.md by inspecting the actual project; write accurate setup and usage guidance with a selectable brand voice, polished information architecture, evidence-based badges and claims, discoverability suggestions, and an optional editable SVG/PNG banner. Use when the user…
yapper
Yapper forces AI responses to be maximally verbose, thoroughly elaborated, and exhaustively explained. All output is expanded by 200–400%. Technical accuracy is maintained at 100%. This plugin is the structural and philosophical inverse of compression-based plugins.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.