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.
git clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/commands/khaledsaeed18/dotclaude/thesis-chapter)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/thesis-chapter"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/thesis-chapter/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/commands/khaledsaeed18/dotclaude/thesis-chapter"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/thesis-chapter.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.00089 | $0.00919 |
| Opus 5.5 | $0.00036 | $0.00368 |
| Sonnet 5.5 | $0.00018 | $0.00184 |
| Haiku 4.5 | $0.00009 | $0.00092 |
Grade A, and why
thesis-chapter scanned grade A with 1 finding 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 25d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Write, Edit, Glob, Grep, Bash(git:*), Bash(ls:*), Bash(find:*), Bash(wc:*), Bash(texcount:*), Bash(pandoc:*), Bash(curl:*) How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Target: $ARGUMENTS
Chapters present:
!ls chapters 2>/dev/null || ls *.tex *.md 2>/dev/null | head -20 || echo "(no chapters directory)"
Research question record (head):
!head -40 research/QUESTION.md 2>/dev/null || echo "(no research/QUESTION.md; run research-question first)"
Notes available:
!ls research/notes 2>/dev/null | wc -l | xargs -I{} echo "{} notes in research/notes/"
Bibliography:
!ls *.bib references/*.bib 2>/dev/null | head -3 || echo "(no .bib found)"
Task
Produce or revise the chapter named in the arguments. A chapter is written once, in full, from an agreed outline; it is not written in fragments across sessions, because the argument has to hold across sections.
Step 1: Establish the inputs
- Resolve the target to a file (
chapters/04-results.tex,chapters/04-results.md, or a new file following the existing naming). With--revise, read the current chapter in full first. - Read
research/QUESTION.md; identify which research questions this chapter serves. - Read the outline for the chapter (a comment block at the top of the file,
research/OUTLINE.md, or the proposal's chapter plan). If there is no outline, write one as a list of claims, one per intended paragraph, show it, and stop for agreement before drafting. - Read every note in
research/notes/marked relevant to this chapter, and any results files or tables it must present.
Step 2: Draft or revise
Apply academic-writing for the section types in this chapter. Constraints:
- Every paragraph starts with its claim.
- Every citation is a key that exists in the
.bib; thecitation-guardhook reports misses as you write. Never add a key that is not in the file; leave[[CITE: what is needed]]for the student. - Every number comes from a results file or a note, with its source in a comment (
% from results/latency.csv row 12or<!-- ... -->). - Figures and tables are referenced by label before they appear; missing ones are placeholders
[[FIG: what it should show]]soresearch-figurescan produce them. - Match the document's format: LaTeX (
\section,\cite,\cref) or Pandoc Markdown (#,[@key],@fig:x). - With
--length, aim within 10% of the target; otherwise use the chapter plan's target or the department norm. - With
--revise, keep the student's sentences where they work; change structure and wording only where the section rules require it, and list what changed.
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.
- 25d ago First seen · 64 lines · 89 tokens per session scan A fbae91eb5522
thesis-chapter is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 89 tokens to every session and 919 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-22.
Other commands, from other repositories
support-model
Write a support model as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
design-doc
Write a design doc / RFC as Markdown in the user's repository. Use when invoked as /document-design-system:design-doc. Produce designed HTML or PDF only when asked.
evaluate
Execute Evaluate stage to validate generated framework artifacts.
tutorial
Write a Diátaxis tutorial as Markdown in the user's repository. Use when invoked as /document-design-system:tutorial. Produce designed HTML or PDF only when asked.
ars-plan
ARS academic-paper plan mode — Socratic chapter-by-chapter planning.
checklist
Generate a custom checklist for the current feature based on user requirements.