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 agentmods add skills/maddhruv/absolute/absolute-specnpx 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.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 | $0.00122 | $0.02265 |
| Opus 5 | $0.00061 | $0.01132 |
| Sonnet 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 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 — 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.
- 4d ago First seen · 217 lines · 122 tokens per session scan A ee195e0303d4
absolute-spec is a skill published in the GitHub repository maddhruv/absolute (209 stars, last pushed 2mo ago), licensed MIT. It adds 122 tokens to every session and 2,265 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-30.
Other skills, from other repositories
data-engineering
Skill "data-engineering" from fengshao1227/ccg-workflow, covering 数据工程域 · data engineering, 域概览, 数据管道编排, 框架对比 and airflow 核心模式.
mobile
移动开发。iOS、Android、SwiftUI、Jetpack Compose、React Native、Flutter、跨平台。当用户提到移动开发、iOS、Android、跨平台时路由到此。.
infrastructure
云原生基础设施。Kubernetes、Helm、Kustomize、Operator、CRD、GitOps、ArgoCD、Flux、IaC、Terraform、Pulumi、CDK。当用户提到 K8s、Helm、GitOps、IaC 时路由到此。.
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.
verify-change
变更校验关卡。分析代码变更，检测文档同步状态，评估变更影响范围。当用户提到变更检查、文档同步、代码审查、提交前检查、diff分析时使用。在设计级变更、重构完成时自动触发。.
verify-quality
代码质量校验关卡。检测复杂度、重复代码、命名规范、函数长度等质量指标。当用户提到代码质量、复杂度检查、代码异味、重构建议、lint检查、代码规范时使用。在复杂模块、重构完成时自动触发。.