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.
npx agentmods add skills/tslateman/duet/debriefnpx skills add tslateman/duet --skill debriefgit clone --depth 1 https://github.com/tslateman/duetWrote 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/tslateman/duet/debrief)<a href="https://agentmods.dev/skills/tslateman/duet/debrief"><img src="https://agentmods.dev/badge/skills/tslateman/duet/debrief.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00303 |
| Opus 5 | $0.00006 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
debrief 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 3d 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
Agent Debrief
Overview
Consolidate work done by agents or across sessions. Review what landed and what's still open.
1. Recent Commits
Check what actually shipped:
git log --oneline -15 --all --decorate
Note any commits from agents or parallel work streams.
2. Work In Progress
Check for uncommitted changes or stashed work:
git status --short
git stash list
3. Synthesis
Produce a brief debrief:
What Landed
- Summarize completed work (be specific, name files, features, fixes)
Loose Ends
- Uncommitted work that needs attention
- Agent work that wasn't fully integrated
- TODOs or FIXMEs introduced
Connections
- Note any overlap or conflicts between parallel work streams
- Flag if multiple changes touched the same files
Next Actions
- Concrete steps to consolidate or continue the work
Keep it actionable. Skip anything that's already clean and integrated.
See Also
The post-agent triad: debrief recaps what got done, the other two check it.
/sweep: post-op check for artifacts, damage, and stale refs left behind/agent-watchdog: audit whether an agent did what was asked, with a gap report and a narrow fix
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.
- 3d ago First seen · 62 lines · 13 tokens per session scan A 76dabd84d976
debrief is a skill published in the GitHub repository tslateman/duet (1 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 303 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
to-roadmap
Capture a multi-task initiative into .task/roadmap/ .md — a phase-grouped backlog of ready-to-pick-up items.
setup-working-genius
Per-repo configuration — pin the work-file directory, verify commands, and issue tracking, seed the project docs, and leave the pointer that tells every future session this project works this way.
genius
The map of the Working Genius workflow — where each piece of work stands, what to run next, and where genius gaps are hiding.
batch
Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.
prep
Spec a ticket before it is dispatched. Brainstorms it, decides everything it can recommend an answer for, asks a present human about the little that survives, and leaves the spec, the decisions and anything still open as one ticket comment. No worktree, no branch, no pull request, and the ticket stays where it was.
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it. Use when asked to work a ticket end-to-end.