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 deep-researchgit 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/deep-research)<a href="https://agentmods.dev/skills/axiomantic/spellbook/deep-research"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/deep-research/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/deep-research"><img src="https://agentmods.dev/badge/skills/axiomantic/spellbook/deep-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.01587 |
| Opus 5.5 | $0.00039 | $0.00635 |
| Sonnet 5.5 | $0.00019 | $0.00317 |
| Haiku 4.5 | $0.00010 | $0.00159 |
Grade A, and why
deep-research 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Research
Announce: "Using deep-research skill for multi-threaded investigation with verification."
Invariant Principles
- Tag Every Claim: No finding without confidence level + source URL
- Surface Every Conflict: When sources disagree, document both positions
- Respect the User's Frame: When research contradicts user-provided facts, STOP and surface conflict via AskUserQuestion. Never silently override.
- Verify Before Synthesizing: All findings pass through fact-checking and dehallucination
Inputs/Outputs
| Input | Required | Description |
|---|---|---|
user_request |
Yes | Research question, topic, or comparison request |
depth |
No | quick (1-2 rounds), standard (3-5), exhaustive (6+) |
Artifacts at ~/.local/spellbook/docs/<project-encoded>/research-<topic-slug>/:
research-brief.md, research-plan.md, micro-reports/, verified-claims.md, research-report.md
Registries
Subject Registry: Track all named entities from request. Each must get >= 1 round. If any subject has 0 rounds after 50% of budget, FORCE a dedicated round.
Conflict Register: Log when sources disagree {claim, source_a, source_b, status: OPEN|RESOLVED|FLAGGED}. All must be RESOLVED or FLAGGED before Phase 4. Choosing one side without citation is FORBIDDEN.
Confidence Tags: VERIFIED (primary source URL) | CORROBORATED (2+ independent) | PLAUSIBLE (consistent, unconfirmed) | INFERRED (derived logically) | UNVERIFIED (no source) | CONTESTED (sources disagree)
Plateau Breaker: URL overlap >= 60% or 0 new facts for 2 rounds triggers: L1 query reformulation, L2 source type change, L3 STOP and report gaps. Before escalating to L3, /deep-research-investigate invokes the fractal-thinking skill at pulse intensity to decompose the research question's hidden assumptions into reframed search angles. Hard limit: 3 stale rounds = mandatory L3.
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 · 130 lines · 97 tokens per session scan A 29bd064ff8e5
deep-research is a skill published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 2d ago), licensed MIT. It adds 97 tokens to every session and 1,587 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-09-03.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
bundle-safety
Bundle transform safety — minification variant selection, consumer-constraint verification, identifier preservation, and namespace re-export coverage for build output.
confirm-failures-are-causally-linked-to-the-task-before-reportin
When delegating a task affected by this skill, include.