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 axiomantic/spellbook --skill estimating-ticketsgit clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/axiomantic/spellbook/estimating-tickets)<a href="https://agentmods.dev/skills/axiomantic/spellbook/estimating-tickets"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/estimating-tickets/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/axiomantic/spellbook/estimating-tickets"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/estimating-tickets.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 Excessive Agency · line 104 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00113 | $0.01648 |
| Opus 5 | $0.00056 | $0.00824 |
| Sonnet 5 | $0.00023 | $0.00330 |
| Haiku 4.5 | $0.00011 | $0.00165 |
Grade A, and why
estimating-tickets 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 5d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bad estimates erode trust. "Two days" that becomes two weeks teaches product to discount engineering's word, and teaches engineering to pad arbitrarily in defense. This skill replaces gut-feel sizing with a reproducible pipeline: scope -> point -> AI-adjust -> PERT-buffer -> Brooks-scale -> report. Every number traces to a step.
Invariant Principles
- Orchestrate, never eyeball: The orchestrator dispatches subagents and invokes phase commands in sequence; direct intuitive estimation in main context is the bias this skill exists to defeat.
- Strict phase order: Pointing without scope is guessing, buffering without pointing is padding, reporting without buffering is unsupported claims. Each phase gates the next.
- Every number traces to a step: A figure that cannot be traced back through the pipeline does not appear in the report. The trace IS the calibration.
- Buffer from sigma, not gut: Uncertainty is quantified via PERT three-point analysis, never an arbitrary fudge factor; always report 80/90/95% bands, never a single number.
- 34 points halts the line: Any ticket reaching 34 points loops back to scope for splitting before estimation continues. Oversized tickets are never estimated as-is.
What ships with it
6 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.
- 5d ago First seen · 111 lines · 113 tokens per session scan A 58ceea167192
estimating-tickets is a skill published in the GitHub repository axiomantic/spellbook (10 stars, last pushed yesterday), licensed MIT. It adds 113 tokens to every session and 1,648 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-09-03.
Other skills, from other repositories
{{BUCKET}}-management
Skill "{{BUCKET}}-management" from damusix/atomic-claude, covering purpose, doc shape and frontmatter contract.
beads-schema
Beads (bd CLI) reference — issue types, statuses, priorities, dependencies, and common commands.
k-roadmap
A planning skill for discovering, breaking down, and delivering large requirements as a shared, gradual feature map.
k-onboard
A guide for creating a repository’s first verified project map and agent collaboration agreement. A project map explains the codebase, while the agreement records how agents should work in it.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
product-clarify
Refine and validate Product Decision Records through targeted clarification questions. Review PDR completeness, detect conflicts, approve decisions, and update status to Accepted. Use before /product-implement.