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/drvoss/everything-copilot-cli/implementation-reviewnpx skills add drvoss/everything-copilot-cli --skill implementation-reviewgit clone --depth 1 https://github.com/drvoss/everything-copilot-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/drvoss/everything-copilot-cli/implementation-review)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/implementation-review"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/implementation-review.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.00036 | $0.01524 |
| Opus 5 | $0.00018 | $0.00762 |
| Sonnet 5 | $0.00007 | $0.00305 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
implementation-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 today.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Review
Implementation review is not ordinary code review. The goal is to verify whether the delivered change actually matches the original task spec, handoff, or review report — and to turn any gaps into a precise follow-up the implementation machine can execute.
When to Use
- A delegated implementation task already landed and you need to check it against the original spec
- Another machine or session reported "done" and shared a commit, branch, or PR
- A task file contained multiple required items and you need item-by-item status
- You want to separate approved, needs correction, missing, and validly excluded
When NOT to Use
| Instead of implementation-review | Use |
|---|---|
| Reviewing code quality or correctness without a prior task spec | code-review |
| Proving that a fix works by rerunning commands | verification-before-completion |
| Turning upstream ecosystem changes into backlog candidates | ecosystem-intake |
| Security-specific review of a change | pr-security-review or agent-owasp-check |
Prerequisites
- You have the original task spec, handoff doc, issue, or review report
- You have the delivered commit hash, branch, PR, or diff range
- You know the intended scope well enough to judge exclusions
Workflow
1. Gather the canonical inputs
Before reviewing the implementation, pin down:
- the original request or task file
- the success criteria or required items
- the delivered commit, branch, or PR
- any stated exclusions or tradeoffs from the implementation pass
If there is no explicit spec, stop and say the review can only assess general quality, not compliance.
2. Inspect the delivered change
Use a stable diff view rather than memory or a narrative summary:
git --no-pager show <commit-hash> --stat
git --no-pager show <commit-hash> --unified=3
# or compare a range
git --no-pager diff <base>...<head>
If the implementation arrived as a PR, review the changed files list first, then inspect the substantive diff.
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.
- today First seen · 188 lines · 36 tokens per session scan A ef13e3233e79
implementation-review is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 1,524 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…
declare
Analyzes task plan and declares files that will be created or modified, producing declared-files.json.
execute
Executes the implementation plan for a Formic task.
launch-command
Launch orchestration and readiness assessment engine with cross-functional workstream tracking and go/no-go gates. Use when: launch readiness, launch checklist, launch orchestration, go no go, launch plan, are we ready to launch.
decompose
Decompose a feature spec into work items for orchestration via nw. Takes a PRD, phase doc, or verbal description and breaks it into human-reviewable PR-sized work items with dependencies mapped into batches. Use when asked to "decompose", "break down this feature", "create work items for", or "plan the work items".
friction-triage
Interactively walk through every friction log in .ninthwave/friction/ one at a time. For each log: read it, assess severity and possible duplicates, ask the human what to do (fix now / create work item / update doc / drop / merge / skip), execute the decision, and delete the log. This is the canonical way to clear the…