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 mthines/agent-skills --skill implement-suggestiongit clone --depth 1 https://github.com/mthines/agent-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/mthines/agent-skills/implement-suggestion)<a href="https://agentmods.dev/skills/mthines/agent-skills/implement-suggestion"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/implement-suggestion/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/mthines/agent-skills/implement-suggestion"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/implement-suggestion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.03606 |
| Opus 5.5 | $0.00035 | $0.01442 |
| Sonnet 5.5 | $0.00017 | $0.00721 |
| Haiku 4.5 | $0.00009 | $0.00361 |
Grade A, and why
implement-suggestion 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 7d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Suggestion
Validate reviewer suggestions on one or more PRs through /critical and /confidence, then hand a suggestion-pack to one worker sub-agent per PR that applies, commits, pushes to the existing branch, and resolves threads.
Never open a new PR.
Detailed procedure lives in rules/*.md; load each file at the phase that names it.
Contents: Mode Detection · Architecture · Multi-PR Workflow · Results · Free-text Workflow · Self-Improvement · Hard Rules · Prerequisites · Rules
Mode Detection
Parse $ARGUMENTS once, in this order. First match wins.
| # | Signal in $ARGUMENTS |
Mode |
|---|---|---|
| 1 | One or more github.com/<owner>/<repo>/pull/<n> URLs (with or without #discussion_r…) |
multi-pr |
| 2 | One bare PR number (#123) and the current directory is a PR worktree |
multi-pr (n=1) |
| 3 | Free-text prose, pasted comment body, or non-PR URL | free-text |
| 4 | Empty and the current branch has an open PR (auto-detected via gh pr view) |
multi-pr (active PR) |
| 5 | Empty and no active PR for the current branch | Prompt the user |
Rule #4 runs gh pr view --json number,url,state,headRefName,headRefOid,isDraft with no number; an OPEN PR becomes the single PR, a MERGED or CLOSED one needs explicit user confirmation.
Full parsing rules: rules/input-parsing.md.
Modifiers (orthogonal to mode):
--watch— loop the single pass on exactly one PR until the reviewers go quiet (max 5 iterations); refuse it with more than one PR or in free-text mode.rules/watch-mode.md— read when--watchis set.--resolve-all— default off; also reply to and resolve every non-fix thread that can honestly be closed.rules/resolve-all.md— read when--resolve-allis set; it changes Phases 3, 5, 6, and 7.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- rules/comment-classification.md 6.5 KB
- rules/comment-fetching.md 17 KB
- rules/handoff.md 13 KB
- rules/input-parsing.md 5.8 KB
- rules/outcome-emit.md 3.8 KB
- rules/resolve-all.md 3.0 KB
- rules/self-improvement-loop.md 15 KB
- rules/validation-gates.md 5.4 KB
- rules/watch-mode.md 11 KB
- rules/worktree-resolution.md 3.3 KB
- templates/suggestion-pack.md 4.8 KB
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.
- 7d ago Changed · -342 lines · -112 tokens per session c5867fe01ff5
- 10d ago Changed 36d50249e251
- 25d ago Changed · -1 lines 9207e56ce34a
- 28d ago Changed · -9 lines · -16 tokens per session 13576bd95cbc
- 1mo ago Changed · -6 lines · -99 tokens per session 8d25f02f1ba2
- 1mo ago Changed 9f1f74124bc3
- 1mo ago Changed · +8 lines 4c1fcce7b8dd
- 1mo ago First seen · 588 lines · 314 tokens per session scan A c0d907748414
implement-suggestion is a skill published in the GitHub repository mthines/agent-skills (20 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 3,606 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-09-03.
Other skills, from other repositories
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
git-workflow
Git best practices, branching strategies, commit conventions, and code review patterns.
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.
azure-repos
Expert knowledge for Azure Repos development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Git/TFVC repos, branch policies/PR checks, CodeQL/secret scanning, ELM sync, or…
gitlab-api
Fetches and analyzes GitLab merge request (MR) comments, metadata, and review feedback using authenticated API calls. Capabilities include fetching comment threads, retrieving reviewer feedback, filtering unresolved discussions, and generating MR activity reports. Use when the user asks about GitLab MR comments, code…