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 maddhruv/absolute --skill absolute-docsgit clone --depth 1 https://github.com/maddhruv/absoluteWrote 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/maddhruv/absolute/absolute-docs)<a href="https://agentmods.dev/skills/maddhruv/absolute/absolute-docs"><img src="https://agentmods.dev/badge/skills/maddhruv/absolute/absolute-docs/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/maddhruv/absolute/absolute-docs"><img src="https://agentmods.dev/badge/skills/maddhruv/absolute/absolute-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 88 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00102 | $0.03769 |
| Opus 5.5 | $0.00041 | $0.01508 |
| Sonnet 5.5 | $0.00020 | $0.00754 |
| Haiku 4.5 | $0.00010 | $0.00377 |
Grade A, and why
absolute-docs 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start your first response with the 📚 emoji.
Absolute Documentations: Diátaxis-Driven Documentation
Absolute Documentations turns "write some docs" into documentation a reader can actually use. Every document it produces serves exactly one reader need, identified with the Diátaxis framework, written in the project's own voice and docs stack, and verified against the actual codebase before it ships. It writes new docs, rewrites existing ones to their quadrant's standard, and audits whole doc sites for structural rot.
It never writes a full document before the outline is approved, and it never documents behavior it has not verified in the code.
The Diátaxis Compass
Every piece of documentation answers exactly one kind of reader need. Classify before writing — a page that mixes quadrants serves nobody.
| Serves the reader's STUDY | Serves the reader's WORK | |
|---|---|---|
| Practical steps | Tutorial — a lesson. Guides a newcomer through a guaranteed-success experience. | How-to guide — a recipe. Helps a competent user accomplish a specific goal. |
| Theoretical knowledge | Explanation — a discussion. Deepens understanding of a topic, gives context and reasons. | Reference — a dictionary. States facts about the machinery, completely and neutrally. |
To classify, ask two questions:
- Is the reader studying (acquiring skill) or working (applying skill)?
- Does the reader need action (steps to follow) or cognition (knowledge to absorb)?
| Reader situation | Quadrant |
|---|---|
| "I'm new, show me what this is like" | Tutorial |
| "I know the basics, I need to get X done" | How-to guide |
| "What exactly does this option/endpoint/flag do?" | Reference |
| "Why does it work this way? What's the bigger picture?" | Explanation |
The cardinal sin is mixing. A tutorial that stops to explain architecture loses the learner. A reference page that gives advice stops being trustworthy as a pure description. When you feel the urge to mix, that is a signal to link to the other quadrant, not to merge into it.
What ships with it
8 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.
- 1mo ago First seen · 346 lines · 102 tokens per session scan A fbf62766c887
absolute-docs is a skill published in the GitHub repository maddhruv/absolute (221 stars, last pushed 3mo ago), licensed MIT. It adds 102 tokens to every session and 3,769 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
glossary-builder
Creates a glossary of key terms for a specific topic or article, with concise plain-language definitions formatted for publication as a sidebar, companion box, or standalone reference.
visual-assets-generation
Generate visual assets (ASCII art, diagrams, banners) for repos and documentation.
README Writer
Generates a professional, comprehensive README.md for any project from its codebase or description.
devtool-quickstart
Create, test, or diagnose a runnable quickstart for a developer tool, API, SDK, connector, or data product. Use for the first working technical task, prerequisites, expected output, troubleshooting, and cleanup; not for a complete onboarding program.
code-to-content
Use when transforming a codebase into developer content. Activates for: Blog posts, tutorials, or technical documentation about code README, changelog, release notes, or API docs generation Twitter/X threads, LinkedIn posts about technical work Conference talk proposals (CFP) or newsletter content Build-in-public…
pitchdocs
Generate marketing-quality repository documentation from codebase analysis. Scans 10 signal categories, extracts features with file-level evidence, and produces README, CHANGELOG, ROADMAP, and 15+ more docs. Zero runtime dependencies. For AI context file management, see ContextDocs.