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-progress)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/thesis-progress"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/thesis-progress/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-progress"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/thesis-progress.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.00096 | $0.00994 |
| Opus 5.5 | $0.00038 | $0.00398 |
| Sonnet 5.5 | $0.00019 | $0.00199 |
| Haiku 4.5 | $0.00010 | $0.00099 |
Grade A, and why
thesis-progress 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 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.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Options: $ARGUMENTS
Today: !date +%Y-%m-%d
Chapter files:
!ls chapters/*.tex chapters/*.md 2>/dev/null || echo "(no chapters directory)"
Raw word counts (markup included; refine below):
!wc -w chapters/*.tex chapters/*.md 2>/dev/null | tail -20
Placeholders:
!grep -rn --include='*.tex' --include='*.md' -E '\[\[(FILL|CITE|FIG|TODO)[^]]*\]\]' chapters 2>/dev/null | wc -l | xargs -I{} echo "{} placeholders"
Reading:
!echo "notes: $(ls research/notes 2>/dev/null | wc -l | tr -d ' '), reading list entries: $(grep -c '^## ' research/reading-list.md 2>/dev/null || echo 0)"
Research log:
!grep -c '^## ' RESEARCH_LOG.md 2>/dev/null | xargs -I{} echo "{} entries"; awk '/^### Open/{f=1;next} /^###|^## /{f=0} f' RESEARCH_LOG.md 2>/dev/null | head -10
Recent activity:
!git log --since='14 days ago' --format=' %ad %s' --date=short 2>/dev/null | head -15
Task
Produce a one-screen status report. Numbers, not adjectives.
Word counts
Use texcount -inc -total -brief for LaTeX or pandoc file -t plain | wc -w for Markdown so markup is excluded. Compare each chapter against its target from the chapter plan (proposal, research/OUTLINE.md, or --target-words split evenly). Show a table: chapter, words, target, percent, placeholders.
Citation health
Count unique cite keys across chapters, keys not in the .bib, and .bib entries with no doi/eprint/url. If research/citation-report.md exists, show its date and totals; if it is older than the newest chapter edit, say a rerun of citation-verifier is due.
Reading
Notes written versus reading-list entries; list entries with no note as the reading backlog (cap at 10).
Open items
The "Open" bullets from the last three log entries, with the age of each (from the entry date). Anything older than 14 days is flagged for the supervisor.
Time
Days to --deadline (or a deadline found in the proposal or research/QUESTION.md). Words remaining divided by days remaining gives the required daily rate; state it, and compare with the actual rate from git history over the last 14 days (words added per day, from git diff --shortstat).
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 · 83 lines · 96 tokens per session scan A 8ad5ad4eff5d
thesis-progress is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 96 tokens to every session and 994 once invoked, about $0.0004 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-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.