agentmods.dev

book.criticize_toc

book.criticize_toc is a skill for Claude Code from gpsaggese/helpers. It costs 15 tokens per session (778 once invoked), scanned A, original, Apache-2.0.

A book table-of-contents review routine that checks chapter topics for errors, ordering problems, missing prerequisites, and audience fit.

In plain words
What is it for?
Use it to review a chapter against nearby chapters and propose specific, ranked changes to its topics and order.
Why use it?
A table of contents can contain factual mistakes or a confusing learning sequence even when the chapters themselves are well written.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

not rated 158repo +1 today A scan 15 tokens original Apache-2.0

Good fit Use it to review a chapter against nearby chapters and propose specific, ranked changes to its topics and order.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/book.criticize_toc
View source ↗ gpsaggese/helpers
Install

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.

Any agent
npx skills add gpsaggese/helpers --skill book.criticize_toc
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

Wrote 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.

agentmods badge for book.criticize_toc

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/book.criticize_toc/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/book.criticize_toc)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/book.criticize_toc"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/book.criticize_toc/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.

agentmods 80×15 button for book.criticize_toc

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/book.criticize_toc"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/book.criticize_toc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 778 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00778
Opus 5.5 $0.00006 $0.00311
Sonnet 5.5 $0.00003 $0.00156
Haiku 4.5 $0.00002 $0.00078

Measured yesterday against content hash ef9fbd7e07de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 yesterday.

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.

.claude/skills/book.criticize_toc/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 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 of a book's chapter (or chapters)
  • Identify mistakes and improvement opportunities, focusing on factual errors over style suggestions
  • Propose concrete, ranked improvements to topics, ordering, scope, and audience fit

Workflow

Read the Material

  • Read .claude/templates/book_map.template.md for the expected TOC structure

  • Read book_map.md, which stores the ### Topics of the book's TOC

    • Read **Title** and **Target audience** at the top of book_map.md
    • Read the # Part heading description the chapter belongs to
    • Read the target chapter's ### Topics that the user refers to
    • Ignore all other sections
      • I.e., ### Lessons, ### Tutorials, ### Related packages, ### Related books, ### Related papers
    • Read the ### Topics of sibling chapters in that Part and the immediate neighbors, chapter N-1 and N+1, to judge continuity

Criticize

  • Read .claude/skills/text.criticize/SKILL.md for general review approaches

  • Evaluate these axes, reporting only high-confidence issues:

    • Internal flow:
      • Order of the ### Topics bullets
      • Prerequisite ordering
      • Redundant or overlapping bullets
      • A bullet that is really two topics
    • 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
    • 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
    • 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

Read the full file on GitHub · 82 lines

Changes

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.

  1. yesterday First seen · 82 lines · 15 tokens per session scan A ef9fbd7e07de

Subscribe to this mod's changes

book.criticize_toc is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 778 once invoked, about $0.0001 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-11-06.

PlanningWriting and docs
Related

book.criticize_toc compared with skills from other repositories

book.criticize_toc next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
book.criticize_tocgpsaggese/helpersSkill158todayApache-2.0A15Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex