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 gpsaggese/helpers --skill book_chapter.fix_headingsgit clone --depth 1 https://github.com/gpsaggese/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/gpsaggese/helpers/book_chapter.fix_headings)<a href="https://agentmods.dev/skills/gpsaggese/helpers/book_chapter.fix_headings"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/book_chapter.fix_headings/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/gpsaggese/helpers/book_chapter.fix_headings"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/book_chapter.fix_headings.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.00016 | $0.01544 |
| Opus 5.5 | $0.00006 | $0.00618 |
| Sonnet 5.5 | $0.00003 | $0.00309 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
book_chapter.fix_headings 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Given a lecture's
.smdsource and its generated.typbook chapter (fromgen_book_chapter.py --mode typst_aima), fix the heading levels and slide-title handling to follow the "Structural Hierarchy" rule in.claude/skills/typst.rules.md - Mostly mechanical (moving
=/==/===markers). A slide title that must become a transition (see Step 3) needs one reworded sentence. That is the only text this skill may change. The rest of the prose stays untouched - A fix-up for chapters generated before that rule existed, or hand-edited inconsistently. On a chapter that already follows the rule, it is a no-op
Inputs
<SMD_FILE>: the lecture source- E.g.,
msml610/lectures_source/Lesson02.1-A_Map_of_Machine_Learning.smd
- E.g.,
<TYP_FILE>: the generated book chapter for<SMD_FILE>- E.g.,
msml610/book/Lesson02.1-A_Map_of_Machine_Learning.typ
- E.g.,
Workflow
Classify Every Heading/slide in <SMD_FILE>
- Walk
<SMD_FILE>top to bottom, collecting every#/##/###(+) heading line and every* Slide Titleline, in source order, with its line number - Track one running flag,
seen_subheading, startingFalse: flip it toTruethe first time a##or deeper heading is seen. Its value when each* Slide Titleline is reached (before any##on the same line updates it) is what Step 3 needs for that slide
Locate the Matching Line in <TYP_FILE>
<TYP_FILE>carries a
comment immediately above every heading/slide it was generated from. Match each Step 1 entry by line number + marker, not by title alone, since titles can repeat (e.g., a lesson and its own first slide sharing a name)// From: <SMD_FILE>:<LINE_NUMBER> '<MARKER> <TITLE>' // Slide: <TITLE>- The heading/title line itself is the next non-comment line after
// Slide: <TITLE>: it may currently be#strong[Title],= Title/== Title/=== Title, or missing entirely (the block's paragraph starts right after the comment, no title line at all)
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.
- yesterday First seen · 108 lines · 16 tokens per session scan A d32e15ff12cc
book_chapter.fix_headings is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 1,544 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.
book_chapter.fix_headings compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| book_chapter.fix_headingsgpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 16 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |