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/causify-ai/helpers/book.criticize_tocnpx skills add causify-ai/helpers --skill book.criticize_tocgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/book.criticize_toc)<a href="https://agentmods.dev/skills/causify-ai/helpers/book.criticize_toc"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/book.criticize_toc.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.00015 | $0.00764 |
| Opus 5 | $0.00008 | $0.00382 |
| Sonnet 5 | $0.00003 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
book.criticize_toc 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Review and criticize the table of content for a chapter (or set of chapters) in a book
- Identify mistakes and improvement opportunities, focusing on factual errors, rather than style suggestions
- Propose concrete, ranked improvements to topics, ordering, scope, and audience fit
Workflow
Step 1: Read the Material
-
Read
.claude/templates/book_map.template.mdfor the expected structure of a table of content of a book -
Read the
book_map.mdthat stores the### Topicsmaking up the table of content for the book- Read
**Title**,**Target audience**at the top ofbook_map.md - Read the
# Partheading description the chapter belongs to - Read the target chapter's
### Topicsthat the user refers to - Ignore the rest of the sections besides
### Topics- I.e.,
### Lessons,### Tutorials,### Related packages,### Related books,### Related papers
- I.e.,
- Read the
### Topicsin the sibling chapters in that Part and the immediate neighbors, chapter N-1 and N+1, to judge continuity
- Read
Step 2: Criticize
-
Read
.claude/skills/text.criticize/SKILL.mdto understand general approaches to review and criticize text -
Evaluate along these axes, reporting only issues you are confident about:
- Internal flow:
- Order of the
### Topicsbullets - Prerequisite ordering
- Redundant or overlapping bullets
- A bullet that is really two topics
- Order of the
- Cross-chapter flow:
- Overlap with neighbors or others in the same Part
- A topic that belongs earlier or later
- Forward references to concepts not yet introduced
- Part fit:
- Does the chapter match the scope description of its
# Part(foundations vs. advanced theory vs. deployment) - Flag misplaced chapters
- Does the chapter match the scope description of its
- Structure conformance:
- Compare the structure to
.claude/templates/book_map.template.md - Report:
- Parts that don't follow the subsections
- Lessons without a FULL/PART/WEAK tag
- References not following
.claude/skills/references.rules.md
- Compare the structure to
- Audience fit:
- Matches the stated audience
- Level too high or low
- Assumed background
- Unexplained jargon
- Scope and balance:
- Too much or too little content for one chapter
- Candidates to split or merge
- Internal flow:
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 · 79 lines · 15 tokens per session scan A 835fdbff8fbd
book.criticize_toc is a skill published in the GitHub repository causify-ai/helpers (145 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 764 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…