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-specgit 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-spec)<a href="https://agentmods.dev/skills/maddhruv/absolute/absolute-spec"><img src="https://agentmods.dev/badge/skills/maddhruv/absolute/absolute-spec/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-spec"><img src="https://agentmods.dev/badge/skills/maddhruv/absolute/absolute-spec.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 10 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.00122 | $0.02265 |
| Opus 5.5 | $0.00049 | $0.00906 |
| Sonnet 5.5 | $0.00024 | $0.00453 |
| Haiku 4.5 | $0.00012 | $0.00227 |
Grade A, and why
absolute-spec 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 — 217 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 Spec
Absolute Spec turns a fuzzy intent into a reviewed design-spec document — then
stops. It is the planning artifact of work, lifted out of the full lifecycle: scan
the codebase, ask only the questions the code can't answer, write the spec, run an
independent scored review, and hand back a doc you can discuss, hand off, or feed into
/absolute work to build.
It is deliberately lightweight. No relentless interview, no task board, no decompose, no execution. One deliverable: a spec good enough that an unfamiliar developer could build from it.
When to use this command
Use spec when:
- You want a design spec to discuss, review, or hand off — not build right now.
- You need to think a feature through on paper before committing to implementation.
- A teammate or another agent will do the building from your spec.
- You want a fast, reviewed design doc without the full phase-gated lifecycle.
Do NOT use spec when:
- You want to design AND build in one flow → use
/absolute work(spec is its Phase 2, followed by decompose + safe-wave execution). - You're documenting code that already exists / already shipped → use
/absolute docs(reference/explanation docs, not a forward design). - The change is a one-line obvious fix needing no design.
The line vs work: spec produces a doc and stops; work produces a doc and then
builds it. If you're unsure whether you'll build it now, start with spec — you can
chain into work afterward and it will pick the spec up.
Key Principles
- Codebase before questions. Read what exists first; ask only what code can't answer.
- Bounded, not relentless. A short clarify pass (3–5 questions), not the depth-first
grill
workruns. Batching questions is fine. - The spec is the deliverable. Quality matters more here than anywhere — keep the independent scored review.
- Reuse, don't reinvent. Template, scaling rules, and review rubric come from
absolute-work'sreferences/spec-writing.md. This command is the thin flow around them. - Stop after review. No code, no board, no execution. Hand off cleanly.
- Never auto-commit. Write the spec file and report; the user commits.
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 First seen · 217 lines · 122 tokens per session scan A ee195e0303d4
absolute-spec is a skill published in the GitHub repository maddhruv/absolute (221 stars, last pushed 3mo ago), licensed MIT. It adds 122 tokens to every session and 2,265 once invoked, about $0.0005 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
ai-loop
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
overdrive
Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.
data-engineering
A guide to data engineering, the work of collecting, moving, processing, and checking data. It covers workflow tools such as Airflow, Dagster, and Prefect, plus streaming and data-quality tools.
animate
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.