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/commands/xyndox/good-bad-ugly/gbu-status)<a href="https://agentmods.dev/commands/xyndox/good-bad-ugly/gbu-status"><img src="https://agentmods.dev/badge/commands/xyndox/good-bad-ugly/gbu-status/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/xyndox/good-bad-ugly/gbu-status"><img src="https://agentmods.dev/badge/commands/xyndox/good-bad-ugly/gbu-status.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.00017 | $0.00199 |
| Opus 5 | $0.00009 | $0.00100 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
gbu-status 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
Herd the currently running good-bad-ugly agents. For each one report:
- State — working, idle, done, or failed.
- Owes a report? — if it went idle without reporting, message it and demand the report format (files changed, net lines, verification results, anything suspicious). Don't accept silence as success.
- Verified? — an agent's "all green" is a claim, not a fact. Flag any work not yet independently re-verified by you (typecheck + full tests) before it gets committed.
- Scope conflicts — any two agents touching the same file, or an agent blaming a failure on "someone else" that was actually your own concurrent edit.
Finish with the next action: who to poll, whose work to verify-and-commit, what to re-spawn or fold inline.
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 · 13 lines · 17 tokens per session scan A f208abdd7b32
gbu-status is a command published in the GitHub repository XyndoX/good-bad-ugly (1 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 199 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-08-31.
Other commands, from other repositories
bigproject
Large-scale project orchestration with Himawari (Atlas).
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
OPSX: Bulk Archive
Archive multiple completed changes at once.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: New
Start a new change using the experimental artifact workflow (OPSX).
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.