Borrowing it
Nothing to install: this file belongs to sussdorff/timing-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sussdorff/timing-cli/main/.agents/skills/session-retro/SKILL.mdgit clone --depth 1 https://github.com/sussdorff/timing-cliWrote 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/sussdorff/timing-cli/session-retro)<a href="https://agentmods.dev/skills/sussdorff/timing-cli/session-retro"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/session-retro/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/sussdorff/timing-cli/session-retro"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/session-retro.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.00047 | $0.00573 |
| Opus 5.5 | $0.00019 | $0.00229 |
| Sonnet 5.5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
session-retro 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Retro
Run at the end of an executive-pack delivery, after the merge or after the pull request
was handed to a human. This skill exists because the Pocock retro skill sets
disable-model-invocation: true and cannot run on its own at the end of a delivery.
1. Retro
Read the installed Pocock retro skill (~/.agents/skills/retro/SKILL.md or
~/.claude/skills/retro/SKILL.md) and apply its method to the finished session. When it
is not installed, review the session for: what cost time or tokens without value, what
failed and why, which review or pr-agent findings were real, which were dismissed and
why, and what the next delivery in this repository should do differently. Keep only
learnings a later session would act on.
2. Encode each learning, structure first
For each learning, in this order:
- Structure in the delivered repository. A lint rule, a test, a check or a script
that makes the mistake impossible or loud. Commit it on a branch in the delivered
repository and open a pull request with
pr; do not merge it here. - Prose, only when no structure can hold it.
- Project learnings go into the delivered repository's
.agents/standards/. - Review-relevant learnings go into
.agents/standards/review.mdthere. A pr-agent finding that was dismissed with a reason is recorded as a dismiss pattern: what the finding looks like, the condition under which it is skipped, and the risk boundary beyond which it must not be skipped. - Cross-project learnings are opened as a pull request against
standards/in cognovis/library-core.
- Project learnings go into the delivered repository's
3. Open Brain
Save the retro with ob save --project <repo> --type session_summary --title "<retro title>" --source-ref <harness>:<session-id> "<text>". The text lists each learning with
where it was encoded (file, pull request link) or why it stayed prose. Report the Open
Brain memory id.
Boundaries
This skill performs no merge, no push of the delivery branch, no issue closure and no worktree cleanup. Its own changes land only through the pull requests it opens.
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 First seen · 52 lines · 47 tokens per session scan A 4ba057892683
session-retro is a skill published in the GitHub repository sussdorff/timing-cli (1 stars, last pushed 10d ago), licensed MIT. It adds 47 tokens to every session and 573 once invoked, about $0.0002 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-29.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…