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 reem-sab/tech-writer-prompts --skill diataxis-classifygit clone --depth 1 https://github.com/reem-sab/tech-writer-promptsWrote 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/reem-sab/tech-writer-prompts/diataxis-classify)<a href="https://agentmods.dev/skills/reem-sab/tech-writer-prompts/diataxis-classify"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/diataxis-classify/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/reem-sab/tech-writer-prompts/diataxis-classify"><img src="https://agentmods.dev/badge/skills/reem-sab/tech-writer-prompts/diataxis-classify.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.00125 | $0.00870 |
| Opus 5 | $0.00063 | $0.00435 |
| Sonnet 5 | $0.00025 | $0.00174 |
| Haiku 4.5 | $0.00013 | $0.00087 |
Grade A, and why
diataxis-classify 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diataxis Classify
Classifies a page against the four Diataxis modes, which are tutorial, how-to guide, reference, and explanation. It identifies passages that belong to a different mode than the primary one of the page, and proposes a concrete split when the mixing is bad enough to matter.
Inputs
{{PAGE}}: The documentation page to classify.
How to apply
Substitute each {{PLACEHOLDER}} above with the user's actual content, then
follow the prompt below exactly — including its output format and its stated
limits.
You are classifying a documentation page against the Diataxis framework's four modes:
- Tutorial — learning-oriented. A guided lesson for a beginner, taking them through a complete experience step by step. Success is "the reader learned something by doing it," not "the reader accomplished a specific real task."
- How-to guide — task-oriented. Steps to accomplish a specific goal, written for someone who already has the basics and wants to get something done. Assumes competence; skips explaining why.
- Reference — information-oriented. Dry, structured, complete description of the system (parameters, options, behavior) — describes, doesn't guide or persuade.
- Explanation — understanding-oriented. Discussion of concepts, design decisions, and the "why" behind the system. Doesn't tell the reader to do anything.
Method
- Determine the page's primary mode from its overall structure and intent — what is it actually trying to help the reader do?
- Scan for passages that belong to a different mode than the primary one. A passage counts as "mixed in" only if it would genuinely serve the reader better on a separate page written for that mode — not every aside or one-sentence rationale is a violation. A how-to guide with one sentence of "why" for a non-obvious step is fine; three paragraphs of conceptual explanation embedded in the middle of numbered steps is not.
- For each mixed-in passage, name which mode it actually belongs to and quote it.
What ships with it
4 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 · 91 lines · 125 tokens per session scan A 350c15486654
diataxis-classify is a skill published in the GitHub repository reem-sab/tech-writer-prompts (4 stars, last pushed 11d ago), licensed MIT. It adds 125 tokens to every session and 870 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…