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/bacchus-labs/wrangler/reviewing-implementation-progressnpx skills add bacchus-labs/wrangler --skill reviewing-implementation-progressgit clone --depth 1 https://github.com/bacchus-labs/wranglerWrote 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/bacchus-labs/wrangler/reviewing-implementation-progress)<a href="https://agentmods.dev/skills/bacchus-labs/wrangler/reviewing-implementation-progress"><img src="https://agentmods.dev/badge/skills/bacchus-labs/wrangler/reviewing-implementation-progress.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.1 | $0.00031 | $0.01475 |
| Opus 5 | $0.00015 | $0.00737 |
| Sonnet 5 | $0.00006 | $0.00295 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
reviewing-implementation-progress 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 6d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing Implementation Progress
Primary Responsibilities
You are provided with:
- Feature specification
- Implementation plan with tasks
- Previously completed task (baseline)
- In-progress task (current work)
Your job is to review all changes between the previously completed task and the in-progress one. Review the full git diff and explore the codebase to ensure:
- Implementation adheres to specification and implementation plan
- Code is high quality, maintainable, follows best practices
- No obvious bugs, security vulnerabilities, or performance issues
- Adequate tests cover new functionality and edge cases
- Tests actually test functionality (not just mocked behavior)
- Outstanding tasks/steps tracked appropriately
Expected Output
Provide findings in structured JSON report:
{
"compliant": false,
"issues": [
{
"type": "specification_mismatch",
"description": "The implementation does not fully adhere to specification. Specifically, it does not support JSON format for structured data exchange as required.",
"location": {
"file": "src/cli/index.ts",
"line": 45
}
},
{
"type": "code_quality",
"description": "Code duplication in agent management module that could be refactored for better maintainability.",
"location": {
"file": "src/agents/agentManager.ts",
"line": 123
}
},
{
"type": "testing_deficiency",
"description": "Unit tests only cover happy path scenarios and do not include edge cases or error handling paths.",
"location": {
"file": "tests/workflowEngine.test.ts",
"line": 67
}
},
{
"type": "performance_issue",
"description": "Synchronous operations in workflow engine have potential bottlenecks that could be optimized with async patterns.",
"location": {
"file": "src/workflowEngine/stateMachine.ts",
"line": 234
}
}
]
}
Issue Types
specification_mismatch
Implementation doesn't match what specification requires. Critical to 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.
- 6d ago First seen · 245 lines · 31 tokens per session scan A 68cfa9153991
reviewing-implementation-progress is a skill published in the GitHub repository bacchus-labs/wrangler (4 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 1,475 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…