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/tdwhere123/do-itWrote 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/tdwhere123/do-it/do-it-retrospective)<a href="https://agentmods.dev/commands/tdwhere123/do-it/do-it-retrospective"><img src="https://agentmods.dev/badge/commands/tdwhere123/do-it/do-it-retrospective/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/tdwhere123/do-it/do-it-retrospective"><img src="https://agentmods.dev/badge/commands/tdwhere123/do-it/do-it-retrospective.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.00010 | $0.00044 |
| Opus 5.5 | $0.00004 | $0.00018 |
| Sonnet 5.5 | $0.00002 | $0.00009 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
do-it-retrospective 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 1mo 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.
What it actually says
Use the do-it-retrospective skill for the episode described by the user. This command does not enable recording, profiles, or automatic policy 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.
- 1mo ago Changed · -7 lines · -32 tokens per session ceb98bce4f4c
- 1mo ago Changed · +9 tokens per session 252c68110bf7
- 1mo ago First seen · 14 lines · 33 tokens per session scan A df6b8cd71c66
do-it-retrospective is a command published in the GitHub repository tdwhere123/do-it (28 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 44 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
tokenless
Show Tokenless status, savings, latest artifact, and style controls.
tokenless-style-chat
Set Tokenless style to chat: shortest readable output.
pu
Extract system improvements from content, monitor external sources, and scan bookmarks for upgrade opportunities. Shortcut for Upgrade skill (formerly PAIUpgrade).
experiment-development
Make a temporary markdown file in /experiments that includes.
generate-code-base-context
in our top level folder can you make a [llms.txt] file that gives all the information needed for all of those files? it should include the main goals for each from a high level, some additional context, but then also list all the functions w/ their params and types as well as concise explanations of functions…