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 flurdy/agent-skills --skill reply-commentsgit clone --depth 1 https://github.com/flurdy/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/flurdy/agent-skills/reply-comments)<a href="https://agentmods.dev/skills/flurdy/agent-skills/reply-comments"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/reply-comments/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/flurdy/agent-skills/reply-comments"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/reply-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Rogue Agent · line 42 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 68 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00038 | $0.02207 |
| Opus 5.5 | $0.00015 | $0.00883 |
| Sonnet 5.5 | $0.00008 | $0.00441 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade A, and why
reply-comments 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 yesterday.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reply to Review Comments
Publish selected, validated feedback outcomes after /review-comments. Push, reply posting, and
thread resolution are three separate visible actions, each requiring fresh current-run
confirmation. Never infer remote permission from item selection, validation, a local commit, a
previous run, or approval of another action.
Usage
/reply-comments # PR for the current branch; select eligible items
/reply-comments 123 # backward-compatible current-repository selector
/reply-comments owner/repo#123 # repository-qualified selector
/reply-comments owner/repo#123 inline:C1 conversation:I2
Arguments identify candidates only. They are not permission to push, post, or resolve.
Instructions
1. Resolve the PR and Checkout
Accept owner/repo#number or a numeric PR. With no selector, resolve the current branch through:
~/.agents/skills/reply-comments/scripts/gh-pr-current-info.sh
Use the selected owner/repository for every GitHub call. Before offering a push, prove the current
checkout's origin, branch, and HEAD correspond to that PR. Do not switch, fetch, reset, clean,
merge, rebase, or overwrite work. A repository mismatch disables the push gate but does not prevent
a separately validated answer/rationale from being prepared.
2. Restore Bounded Handled State
Carry forward /review-comments state when it exists. Otherwise reconstruct validation and prepared
replies read-only before offering any remote action. Keep at most 500 handled actions keyed by
repository/PR/identity/updateKey, recording validation, commit SHA, push result, posted reply ID,
and resolution result.
On retry:
- a recorded successful push, reply, or resolution is not repeated;
- an inline record with a later self reply is treated as already replied;
- an already resolved thread is recorded as complete without another mutation;
- an uncertain or timed-out mutation result is reported as unknown — do not retry automatically;
- if bounded state was lost, announce that idempotency continuity is unavailable and require a read-only recheck plus new confirmations. For a top-level response whose prior publication cannot be disproved from current self-comments, do not offer another post; return it for manual reconciliation.
What ships with it
7 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.
- scripts/gh-pr-comments.sh 174 B runs code
- scripts/gh-pr-conversation-comment.sh 272 B runs code
- scripts/gh-pr-current-info.sh 185 B runs code
- scripts/gh-pr-reply-comment.sh 301 B runs code
- scripts/gh-pr-resolve-thread.sh 331 B runs code
- scripts/gh-pr-review-threads.sh 545 B runs code
- tests/test-attended-contract.sh 3.8 KB runs code
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.
- yesterday Changed · +5 lines 8e8af17e1df2
- 4d ago Changed 42a7f09995cb
- 9d ago Changed · +5 lines db54681bd4eb
- 1mo ago First seen · 193 lines · 38 tokens per session scan A a510a3d98888
reply-comments is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 2,207 once invoked, about $0.0002 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.