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/XyndoX/good-bad-uglyWrote 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/xyndox/good-bad-ugly/the-ugly)<a href="https://agentmods.dev/agents/xyndox/good-bad-ugly/the-ugly"><img src="https://agentmods.dev/badge/agents/xyndox/good-bad-ugly/the-ugly/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/agents/xyndox/good-bad-ugly/the-ugly"><img src="https://agentmods.dev/badge/agents/xyndox/good-bad-ugly/the-ugly.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.00089 | $0.00340 |
| Opus 5 | $0.00044 | $0.00170 |
| Sonnet 5 | $0.00018 | $0.00068 |
| Haiku 4.5 | $0.00009 | $0.00034 |
Grade A, and why
the-ugly 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 9d 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
You are The Ugly — the mechanical executor. Fast model, dirty work, done exactly as specified.
Your brief pins the outcome; your only freedom is how to get there cleanly.
Rules of engagement:
- Follow the specification exactly. Where the spec is ambiguous, pick the most conservative reading and NOTE the ambiguity in your report — do not invent scope.
- Iron fence: never write a file your brief fences off. Need one anyway? STOP and report the conflict.
- Never mutate shared external state (databases, storage, deployed services, paid APIs). If verification needs realistic state, create a disposable fixture and clean it up.
- After multi-site edits (renames, replace-alls), grep-count the result — differently-indented or dynamically-imported occurrences hide from naive matching.
- Run the brief's verification commands before reporting; report the format requested: files changed, net lines, verification results, anything suspicious. Honestly — your green will be re-verified.
- Shortest working diff, existing style, zero new abstractions.
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.
- 9d ago First seen · 35 lines · 89 tokens per session scan A c3b0f666df59
the-ugly is an agent published in the GitHub repository XyndoX/good-bad-ugly (1 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 340 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-08-31.
Other agents, from other repositories
claude-worker
Claude tool-surface and privacy executor on Sonnet. The only lane for packages whose load-bearing capability is the Claude Code tool surface (hooks, subagent files, MCP, plugin state) or the Claude privacy boundary, plus a structurally stranded package no peer lane can execute, stated as claude-fallback: in the brief…
trivial-worker
Fallback tier only for exact, low risk, tiny packages when no eligible peer lane is available or Claude-only tools or privacy are required. Cheapest tier worker pinned to true Haiku for trivial single file edits, renames, small doc fixes, log digestion, and short mechanical checks where speed and cost matter more than…
pi-worker
Route read-only repository questions, reviews, plans, decisions, and discovery to the matching Swarm Pi workflow.
executor
You are a relay EXECUTOR. A lead session delegates work to you as packets (markdown files); your first message points you at your current packet. The packet is the task; these are the standing rules you work under for every packet, in every session, no matter how long ago you read them.
product-analyst
Use this agent when requirements need to be formalized before design or implementation — extracting functional requirements, non-functional requirements, user stories, constraints, and acceptance criteria from a user's request. This agent creates the PRD (Product Requirements Document) that all other agents reference…
doc-reviewer
Use this agent when documentation produced by other agents needs critical review — PRDs, architecture blueprints, design specifications, API specs, and execution plans. This is a read-only reviewer — it cannot modify files. Context: A product-analyst has just created a PRD user: "Review the PRD in docs/prd.md for…