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 specter119/skills --skill thorough-digestgit clone --depth 1 https://github.com/specter119/skillsWrote 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/specter119/skills/thorough-digest)<a href="https://agentmods.dev/skills/specter119/skills/thorough-digest"><img src="https://agentmods.dev/badge/skills/specter119/skills/thorough-digest/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/specter119/skills/thorough-digest"><img src="https://agentmods.dev/badge/skills/specter119/skills/thorough-digest.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00058 | $0.00487 |
| Opus 5.5 | $0.00023 | $0.00195 |
| Sonnet 5.5 | $0.00012 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
thorough-digest 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 2mo 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.
What it actually says
Thorough Digest
Responsible for exhaustive processing and parallel synthesis of local materials; does not handle external web research.
USE FOR
- Batch processing of local files, directories, sections, or material collections
- Item-by-item extraction of key points with no items allowed to be skipped
- Building a unified narrative or comprehensive report from existing materials
DO NOT USE FOR
- Requires fetching new information from the web
- Only processing one or two documents
- The primary goal is writing slides or a formal report rather than first digesting materials
Execution Skeleton
- First inventory all input items to ensure the scope is clear.
- Follow workflow to determine grouping and parallelization strategy.
- Give each sub-agent an explicit item list, output path, and the constraint that no items may be skipped.
- Aggregate findings from each group; if needed, chain an external research skill to fill gaps.
Reference Map
- workflow: phased workflow, grouping strategy, output structure
- guidelines: parallelization granularity, error handling, best practices
- templates: inventory / classify / sub-agent / synthesis templates
- trigger-cases: minimal trigger examples
- execution-cases: key execution scenarios
- optimization-notes: current refactor rationale
Output Contract
- Default deliverables: inventory, grouping results, per-group findings, and final synthesis
- Must be able to report total input count, processed count, and coverage status
Collaboration and Handoff
- If the synthesis phase reveals critical fact gaps, hand off to an external research skill
- If materials are fully digested and the next step is writing a formal deliverable, hand off to a writing or presentation-structure skill
What ships with it
7 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.
- 2mo ago First seen · 51 lines · 58 tokens per session scan A 85d57326745b
thorough-digest is a skill published in the GitHub repository specter119/skills (2 stars, last pushed 8d ago), licensed MIT. It adds 58 tokens to every session and 487 once invoked, about $0.0002 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…