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/dedupe)<a href="https://agentmods.dev/commands/twaldin/hone/dedupe"><img src="https://agentmods.dev/badge/commands/twaldin/hone/dedupe/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/dedupe"><img src="https://agentmods.dev/badge/commands/twaldin/hone/dedupe.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.00005 | $0.00533 |
| Opus 5 | $0.00003 | $0.00267 |
| Sonnet 5 | $0.00001 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
dedupe 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
Issue deduplication command
Find up to 3 likely duplicate issues for a given GitHub issue.
To do this, follow these steps precisely:
- Use an agent to check if the GitHub issue (a) is closed, (b) does not need to be deduped (eg. because it is broad product feedback without a specific solution, or positive feedback), or (c) already has a duplicate detection comment (check for the exact HTML marker
<!-- dedupe-bot:marker -->in the issue comments - ignore other bot comments). If so, do not proceed. - Use an agent to view a GitHub issue, and ask the agent to return a summary of the issue
- Then, launch 5 parallel agents to search GitHub for duplicates of this issue, using diverse keywords and search approaches, using the summary from Step 2. IMPORTANT: Always scope searches with
repo:owner/repoto constrain results to the current repository only. - Next, feed the results from Steps 2 and 3 into another agent, so that it can filter out false positives, that are likely not actually duplicates of the original issue. If there are no duplicates remaining, do not proceed.
- Finally, comment back on the issue with a list of up to three duplicate issues (or zero, if there are no likely duplicates)
Notes (be sure to tell this to your agents, too):
- Use
ghto interact with GitHub, rather than web fetch - Do not use other tools, beyond
gh(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 - For your comment, follow the following format precisely (assuming for this example that you found 3 suspected duplicates):
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
- If your issue is a duplicate, please close it and 👍 the existing issue instead
- To prevent auto-closure, add a comment or 👎 this comment
🤖 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 · 44 lines · 5 tokens per session scan A 7b6d70fd11bb
dedupe is a command published in the GitHub repository twaldin/hone (47 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 533 once invoked, about $0.0000 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
report-issue-with-atomic
Open an issue against the atomic-claude repo itself (bugs/feature requests with the installed config, not the user's current project).
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
roadmap-track.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
vision-adjust.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
vision-init.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
create-github-epic.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.