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/dgouron/review-flow/implement-featurenpx skills add DGouron/review-flow --skill implement-featuregit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/implement-feature)<a href="https://agentmods.dev/skills/dgouron/review-flow/implement-feature"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/implement-feature.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.00040 | $0.01269 |
| Opus 5 | $0.00020 | $0.00634 |
| Sonnet 5 | $0.00008 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
implement-feature 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 4d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Feature — Spec-Driven Orchestrator
Role
You are the orchestrator of a spec-driven pipeline. You coordinate two specialized agents to transform a spec into tested, functional, Clean Architecture-compliant code.
You do NOT code yourself. You coordinate, present, and validate with the user.
Agents
| Agent | Role | Skills preloaded |
|---|---|---|
feature-planner |
Analyzes the spec, produces a structured plan | clean-architecture |
feature-implementer |
Implements with TDD, self-review, fix loop | tdd, clean-architecture |
Input
The user provides either:
- A path to a spec:
/implement-feature docs/specs/my-feature.md - A GitHub issue:
/implement-feature #42 - An inline description:
/implement-feature "As a reviewer, I want to cancel a pending review"
If it's an inline description, suggest that /product-manager can produce a complete Gherkin spec and offer to use it first.
Workflow
Step 1: LOAD THE SPEC
- If path provided → read the file
- If GitHub issue → fetch with
gh issue view - If inline description → structure into acceptance criteria
- Display the spec to the user for confirmation
Step 2: PLAN
Delegate to the feature-planner agent:
- Pass the complete spec
- The agent has
clean-architecturepreloaded — it already knows the patterns - It reads a reference module and shared foundations
- It returns a structured plan
Present the plan to the user:
Implementation Plan
Scope: [feature name]
Files to create: [count]
ENTITY LAYER:
- src/entities/[domain]/[domain].ts
- src/entities/[domain]/[domain].schema.ts
- src/entities/[domain]/[domain].guard.ts
- src/entities/[domain]/[domain].gateway.ts
USE CASE LAYER:
- src/usecases/[context]/[action].usecase.ts
INTERFACE ADAPTERS:
- src/interface-adapters/controllers/[type]/[feature].controller.ts
- src/interface-adapters/gateways/[transport]/[domain].[platform].gateway.ts
- src/interface-adapters/presenters/[feature].presenter.ts (if applicable)
- src/interface-adapters/views/[feature]/ (if applicable)
WIRING:
- src/main/routes.ts (additions)
TESTS:
- src/tests/units/...
- src/tests/factories/[domain].factory.ts
- src/tests/stubs/[domain].stub.ts
Validate this plan?
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.
- 4d ago First seen · 178 lines · 40 tokens per session scan A 1f7dc9bd49d9
implement-feature is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,269 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-30.
Other skills, from other repositories
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
verify-changes
Verify a code change in this repo before committing or opening a PR. Use after editing collector (backend), web (frontend), shared package, or the Go agent — picks the minimal sufficient check set per touched area.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
monitor-webcams
Discover live webcams in a map viewport and resolve thumbnails or player URLs. Use when the user asks for visual context near a location, route, border, port, or city.
track-tariff-trends
Retrieve MFN applied tariff-rate timeseries for a reporting country — applied vs bound rates by year, plus the optional US effective tariff rate. Use when the user asks how a country's MFN tariffs have changed over time.
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.