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 skills add uvwt/agentdock-skills --skill code-debriefgit clone --depth 1 https://github.com/uvwt/agentdock-skillsWrote 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/uvwt/agentdock-skills/code-debrief)<a href="https://agentmods.dev/skills/uvwt/agentdock-skills/code-debrief"><img src="https://agentmods.dev/badge/skills/uvwt/agentdock-skills/code-debrief/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/uvwt/agentdock-skills/code-debrief"><img src="https://agentmods.dev/badge/skills/uvwt/agentdock-skills/code-debrief.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.00078 | $0.01279 |
| Opus 5.5 | $0.00031 | $0.00512 |
| Sonnet 5.5 | $0.00016 | $0.00256 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
code-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 29d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read the real code before explaining it. Do not guess paths, behavior, dependencies, runtime order, or design intent. If a fact can be established from the codebase, Git diff, configuration, or minimal runtime observation, inspect it instead of asking the user.
The goal is learning: help the user understand and retain control of code produced through vibecoding. Start from the current project and then extract transferable engineering knowledge. Do not turn the session into a generic code review, refactoring backlog, test audit, or project-management report.
Scope
Determine the learning scope in this order:
- An explicitly supplied PR, commit, commit range, diff, file, directory, symbol, or feature.
- Current staged changes.
- Current unstaged changes.
- The most recent relevant commit.
- The user's natural-language target.
Use the selected change as the center, then inspect only the upstream and downstream code needed to explain it: entry points, direct callers, direct dependencies, important types, data/state transitions, configuration that changes behavior, and critical failure paths.
Do not mechanically explain the whole repository or every changed file.
Default interaction
Default to continuous explanation. Do not force questions after every section.
Only ask a single optional learning question when it materially helps verify a core mental model, and let the user skip it. If the user asks to be quizzed or taught interactively, switch to learning mode and ask one question at a time.
Explanation order
Use this flexible learning skeleton, adapting the order to the code type and real execution path:
- What problem or capability this code implements.
- Where execution enters.
- The main call chain or state flow.
- The smallest set of core code that makes the behavior work.
- Inputs, outputs, side effects, and state/data changes.
- Important failure or alternate paths.
- Why the code is organized this way.
- The general engineering idea that can be transferred elsewhere.
- Where to start when the user later wants to modify the behavior.
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.
- 29d ago Changed · -1 lines 3f2b8bf39955
- 1mo ago First seen · 120 lines · 78 tokens per session scan A 42f53339dc30
code-debrief is a skill published in the GitHub repository uvwt/agentdock-skills (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,279 once invoked, about $0.0003 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-31.
Other skills, from other repositories
math-olympiad
Solve competition math problems (IMO, Putnam, USAMO, AIME) with adversarial verification that catches the errors self-verification misses. Activates when asked to 'solve this IMO problem', 'prove this olympiad inequality', 'verify this competition proof', 'find a counterexample', 'is this proof correct', or for any…
google-agents-cli-onboarding
Onboarding entrypoint for agents-cli in Agent Platform. It should be used when the user wants to "create a new agent", "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "evaluate an agent", "deploy an agent", "publish an agent", "monitor an agent", or needs…
edu-math-tutorial
A Chinese-language guide for turning a maths problem into a step-by-step teaching video. It explains how to break down the solution, write narration, format equations, and structure scenes.
math-tools
Deterministic mathematical computation using SymPy. Use for ANY math operation requiring exact/verified results - basic arithmetic, algebra (simplify, expand, factor, solve equations), calculus (derivatives, integrals, limits, series), linear algebra (matrices, determinants, eigenvalues), trigonometry, number theory…
huashu-speech-coach
A coach for preparing talks, presentations, training sessions, technical talks, and tutorial videos, based on Patrick Winston’s How to Speak approach.
practice-cognition
A method for testing ideas in practice, learning from the results, and improving the next attempt through repeated cycles.