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.
git clone --depth 1 https://github.com/twaldin/honeWrote 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/commands/twaldin/hone/find-duplicate-prs)<a href="https://agentmods.dev/commands/twaldin/hone/find-duplicate-prs"><img src="https://agentmods.dev/badge/commands/twaldin/hone/find-duplicate-prs/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/commands/twaldin/hone/find-duplicate-prs"><img src="https://agentmods.dev/badge/commands/twaldin/hone/find-duplicate-prs.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00822 |
| Opus 5 | $0.00005 | $0.00411 |
| Sonnet 5 | $0.00002 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
find-duplicate-prs 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.
What it actually says
Find duplicate PRs command
Find other open, unmerged pull requests that may be duplicates of (or substantially overlap with) a given PR.
To do this, follow these steps precisely:
- Use an agent to check if the PR (a) is closed/merged, or (b) already has a duplicate-PR comment (check for the exact HTML marker
<!-- find-duplicate-prs-bot:marker -->in the PR comments — ignore other bot comments). If so, do not proceed. - Use an agent to view the PR title, body, and diff (
gh pr viewandgh pr diff), and ask the agent to return a summary of:- What the PR changes (files modified, functions changed, features added/fixed)
- Key technical terms, error messages, API names, or module names involved
- Any issue numbers referenced (e.g. "fixes #123") — two PRs that fix the same issue are likely duplicates
- Then, launch 3 parallel agents to search GitHub for other open, unmerged pull requests that may duplicate this one, using diverse keywords derived from the summary in Step 2. IMPORTANT: Always scope searches with
repo:owner/repo is:pr is:open is:unmergedto constrain results to the current repository. Each agent should try a different search strategy:- Agent 1: Search using the PR title keywords and referenced issue numbers
- Agent 2: Search using
gh pr listfiltered by the same files/paths touched in the diff - Agent 3: Search using feature/API/function names from the changed code
- Next, feed the results from Steps 2 and 3 into another agent, so that it can filter out false positives that are not actually duplicates. Exclude the PR itself. Only keep PRs that change the same code area for the same purpose, or fix the same referenced issue. If there are no likely duplicates remaining, do not comment at all — silently exit.
- Finally, if and only if at least one likely duplicate was found, comment on the PR.
Notes (be sure to tell this to your agents, too):
- Use
ghto interact with GitHub, rather than web fetch - You may also use read-only
gitcommands (git diff,git log,git show,git grep, etc.) against the local checkout - Do not use other tools beyond
ghandgit(eg. don't use other MCP servers, file edit, etc.) - Make a todo list first
- Always scope searches with
repo:owner/repoto prevent cross-repo false positives - Only match against open, unmerged PRs — do not suggest closed, merged, or draft PRs
- Never include the input PR in the results
- Do not post a comment if zero duplicates are found
- For your comment, follow the following format precisely (assuming for this example that you found 2 likely duplicates):
This PR may be a duplicate of:
🤖 Generated with Claude 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 First seen · 48 lines · 10 tokens per session scan A f54b0f0a6adc
find-duplicate-prs is a command published in the GitHub repository twaldin/hone (47 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 822 once invoked, about $0.0001 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-07.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.
mach12:pr-review-assessment
Independently assess each finding from a PR review and classify it.
mach12:pr-review-fix
Fix specific issues identified in a PR review.
align
Context-aware alignment. When in plan mode, it reviews the active plan. Otherwise, it reviews all branch changes against Ion quality gates and principles, implements the fixes and commits them after operator approval.
mach12:pr-review
Run a comprehensive PR review with independent reviewers and post the results as a structured comment.