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/hoangsonww/forge-agentic-coding-cli/dedupe-beadsnpx skills add hoangsonww/Forge-Agentic-Coding-CLI --skill dedupe-beadsgit clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLIWrote 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/hoangsonww/forge-agentic-coding-cli/dedupe-beads)<a href="https://agentmods.dev/skills/hoangsonww/forge-agentic-coding-cli/dedupe-beads"><img src="https://agentmods.dev/badge/skills/hoangsonww/forge-agentic-coding-cli/dedupe-beads.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.00036 | $0.00219 |
| Opus 5 | $0.00018 | $0.00110 |
| Sonnet 5 | $0.00007 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
dedupe-beads 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 3d 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.
What it actually says
/dedupe-beads
Large bead batches (100+) always develop duplicates. Run this as a dedicated pass; don't try to do it inline during polishing.
Prompt
Use the verbatim prompt at .flywheel/prompts/dedupe-beads.md.
Merge rules
For each pair merged:
- Keep the richest description between the pair.
- Take the union of
depends_onandblocksedges (dedupe). - Keep the higher priority (lower number wins).
- Preserve every test obligation from both beads.
- Update any bead in
.beads/beads.jsonlthat referenced the deprecated id.
Close vs delete
Prefer closing merged-away beads with a closed_reason pointing to
the canonical id, rather than deleting the line. Keeps the audit
trail clean.
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.
- 3d ago First seen · 31 lines · 36 tokens per session scan A d893e1e54467
dedupe-beads is a skill published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (22 stars, last pushed 18d ago), licensed MIT. It adds 36 tokens to every session and 219 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
code-reviewer
Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, git diff, code edits, quality mentions.
git-commit-helper
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
test-generator
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.
api-documenter
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.
readme-updater
Keep README files current with project changes. Use when project structure changes, features added, or setup instructions modified. Suggests README updates based on code changes. Triggers on significant project changes, new features, dependency changes.
dependency-auditor
Check dependencies for known vulnerabilities using npm audit, pip-audit, etc. Use when package.json or requirements.txt changes, or before deployments. Alerts on vulnerable dependencies. Triggers on dependency file changes, deployment prep, security mentions.