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/weekly-review)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/weekly-review"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/weekly-review/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/weekly-review"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/weekly-review.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.00097 | $0.00972 |
| Opus 5.5 | $0.00039 | $0.00389 |
| Sonnet 5.5 | $0.00019 | $0.00194 |
| Haiku 4.5 | $0.00010 | $0.00097 |
Grade A, and why
weekly-review 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 24d 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 — 73 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 | Week start: !date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d
Commits this week (all branches):
!git log --all --since='7 days ago' --format=' %ad %h %s (%an)' --date=short 2>/dev/null | head -40
Pull requests touched this week:
!gh pr list --state all --search "updated:>=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)" --json number,title,state,mergedAt,author --jq '.[] | " #\(.number) [\(.state)] \(.title)"' 2>/dev/null | head -20
Issues closed this week:
!gh issue list --state closed --search "closed:>=$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)" --json number,title --jq '.[] | " #\(.number) \(.title)"' 2>/dev/null | head -20
Decision log and research log entries this week:
!grep -h "^- $(date +%Y-%m)" DECISIONS.md docs/DECISIONS.md 2>/dev/null | tail -10; grep -c "^## $(date +%Y-%m)" RESEARCH_LOG.md 2>/dev/null | xargs -I{} echo "{} research log entries this month"
Previous review's plan:
!f=$(ls reviews/*.md docs/reviews/*.md 2>/dev/null | sort | tail -1); [ -n "$f" ] && awk '/^## Next week/{f=1;next} /^## /{f=0} f' "$f" | head -15 || echo "(no previous review)"
Task
Write reviews/<week-end-date>.md (or the existing reviews directory). Use --since to change the window and --author to filter commits to one person in a shared repo.
Structure
# Week ending 2026-09-21
## Done
- Shipped: PR #45 workflow-hooks (merged Tue). Evidence: link.
- ...
Grouped by theme, each with its evidence (commit, PR, issue, file). Nothing without evidence.
## Against last week's plan
| Planned | Outcome |
| Finish thesis chapter 2 outline | done (research/OUTLINE.md) |
| Run n=30 sweep | not started; blocked on GPU quota |
## Decisions
- From DECISIONS.md and meeting notes this week, one line each.
## Stalled or overdue
- Action items past due (from meeting notes, the research log's Open section, open PRs with no activity for 5+ days).
## Numbers
Commits, PRs merged, issues closed, notes written, words added to chapters (if a thesis is present, from git diff --shortstat on chapters/).
## Next week
- Three to five outcomes, each with a definition of done and, where useful, a day.
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.
- 24d ago First seen · 73 lines · 97 tokens per session scan A 47d213a95403
weekly-review is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 972 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
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.
ship
Command "ship" from ngocsangyem/MeowKit, covering /ship — phase 5: ship pipeline, usage, behavior, pre-conditions and execution steps.
commit
Create a commit with validation (lint + tests) — optionally pass the message.
help
List the available commands.
done
Finalize changes — quick review + check + commit.