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 tomzx/agents --skill divio-documentationgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/divio-documentation)<a href="https://agentmods.dev/skills/tomzx/agents/divio-documentation"><img src="https://agentmods.dev/badge/skills/tomzx/agents/divio-documentation.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.00052 | $0.01404 |
| Opus 5 | $0.00026 | $0.00702 |
| Sonnet 5 | $0.00010 | $0.00281 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
divio-documentation 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 4d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Divio Documentation
Writes or reviews documentation following the Divio/Diátaxis four-type system, ensuring each document serves its intended audience and purpose without mixing concerns.
Prerequisites
- The subject to document or the document to review provided in context
- Clarity on which documentation type is needed (or ask to determine it)
- Target audience's knowledge level
Decision Framework
Identify the type before writing:
Is the user studying or working?
/ \
Studying Working
| |
v v
Is it practical Is it practical
or theoretical? or theoretical?
/ \ / \
Pract. Theor. Pract. Theor.
| | | |
v v v v
Tutorial Expl. How-to Ref.
Quick identification:
- "I want to learn X" -> Tutorial
- "I want to accomplish Y" -> How-to
- "What are the parameters of Z?" -> Reference
- "Why does X work this way?" -> Explanation
The Four Documentation Types
1. TUTORIALS (Learning-Oriented)
Purpose: Take a complete beginner through steps to complete a meaningful project and gain confidence.
Audience: Absolute beginners with minimal prior knowledge.
DO:
- Start from zero, make no assumptions about prior knowledge
- Provide concrete, specific steps that are reliably repeatable
- Make every step produce a visible, comprehensible result
- Keep the learner moving forward at all times
- End each section with a meaningful accomplishment
DON'T:
- Explain concepts or theory in depth (link to Explanation instead)
- Provide options or alternatives (one clear path only)
- Allow the learner to encounter errors or confusion
- Discuss edge cases or advanced features
Structure:
# Tutorial: [Specific Achievement]
## What You'll Build
## Prerequisites
## Step 1: [Action Verb + Specific Task]
## Step 2: [Next Action]
## What You've Learned
## Next Steps
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.
- 4d ago First seen · 205 lines · 52 tokens per session scan A 4680971fc946
divio-documentation is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 1,404 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-09-03.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.