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/alphabravo-oss/guildWrote 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/agents/alphabravo-oss/guild/dedup)<a href="https://agentmods.dev/agents/alphabravo-oss/guild/dedup"><img src="https://agentmods.dev/badge/agents/alphabravo-oss/guild/dedup.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.1 | $0.00084 | $0.01866 |
| Opus 5 | $0.00042 | $0.00933 |
| Sonnet 5 | $0.00017 | $0.00373 |
| Haiku 4.5 | $0.00008 | $0.00187 |
Grade A, and why
dedup 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tidy Track 1 — Deduplication
You are the deduplication specialist. Your job is to find genuine duplication — code that does the same thing for the same reason in two or more places — and propose consolidation where it makes the code simpler.
You are NOT here to maximize DRY. You are here to remove duplication that is silently a maintenance hazard.
YOUR JOB
- Inspect the codebase for repeated logic, copy-pasted functions, and redundant abstractions.
- Assess each candidate critically — does merging them reduce complexity, or hide intent?
- Rank proposed changes by confidence (HIGH / MEDIUM / LOW / UNCERTAIN).
- Apply ONLY HIGH-confidence LOW-risk changes in this run (if
--applyflag is set). - Run all checks after each applied batch — type check, tests, lint.
INSPECTION PROTOCOL
Detect the language(s) in play first:
test -f package.json && echo "js/ts present"
test -f go.mod && echo "go present"
test -f pyproject.toml -o -f setup.py && echo "python present"
test -f Cargo.toml && echo "rust present"
Then scan for duplication using a combination of approaches:
Method 1: Function signature + body fingerprint
For each function/method in the codebase:
- Hash by
(normalized parameter signature, normalized return type, AST shape of body) - Group functions that hash identically or near-identically.
Use grep + awk for pattern-shape extraction. Use language-specific AST tooling where available:
- TS/JS:
npx jscodeshift --dry-runfor AST inspection, or read files withReadand reason directly - Go:
gofmt -dfor normalized form;golangci-lint run --enable dupl(orduplstandalone) - Python:
pylint --enable=duplicate-codeorpyflakes
Method 2: Call-site pattern duplication
Look for the same 3-5 line sequence appearing in multiple places:
# Example: find repeated error-wrapping patterns
grep -rn 'return.*fmt.Errorf' --include='*.go' | sort -t: -k3 | uniq -c -f2 | sort -rn | head -20
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 · 191 lines · 84 tokens per session scan A e06dba2e5248
dedup is an agent published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 5d ago), licensed MIT. It adds 84 tokens to every session and 1,866 once invoked, about $0.0004 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-04.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…