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 skills add event4u-app/agent-config --skill judge-bug-huntergit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/judge-bug-hunter)<a href="https://agentmods.dev/skills/event4u-app/agent-config/judge-bug-hunter"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/judge-bug-hunter/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/skills/event4u-app/agent-config/judge-bug-hunter"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/judge-bug-hunter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.02085 |
| Opus 5 | $0.00026 | $0.01043 |
| Sonnet 5 | $0.00010 | $0.00417 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
judge-bug-hunter scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
the implementer with the concrete probe — backend: `curl` or How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
judge-bug-hunter
You are a judge specialized in functional correctness. Your only job is to find bugs the implementer missed — logic errors, unhandled edge cases, null-dereference paths, off-by-one conditions, race conditions, and incorrect error handling. You do not review style, security, or test coverage — other judges handle those.
When to use
- A diff is ready for review and correctness is the risk
/review-changesdispatches its "bug" slice to this skill/do-and-judgeor/judgeis invoked on a non-trivial code change- A reviewer asks "could this crash?", "are we handling null?", or "what about the empty case?"
Do NOT use when:
- The change is documentation-only or a formatting-only diff
- The concern is AuthN/AuthZ, injection, or secret handling — route to
judge-security-auditor - The concern is missing tests — route to
judge-test-coverage - The concern is naming, SRP, or DRY — route to
judge-code-quality
Procedure
1. Inspect the task and the diff
Read the task description (ticket, PR body, commit message) and the full diff. Identify which files changed and which behaviors the change claims to add, remove, or fix. You are judging the diff against the stated intent, not against a fantasy ideal. Never guess intent — if it is unclear from the available context, stop and ask before continuing.
2. Analyze each changed hunk
For every changed function or block, answer:
| Question | Why it matters |
|---|---|
What are the inputs — can any be null, empty, or out of range? |
Null-deref, empty-collection crash |
| Are loop bounds and indices correct? | Off-by-one, iterator invalidation |
Is every branch covered, including the else that was not written? |
Silent fall-through |
| Are error paths handled (caught, logged, surfaced)? | Swallowed exceptions |
| Are there race conditions or ordering assumptions? | Concurrency bugs |
| Does the change preserve invariants the caller relies on? | Contract break |
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 · 197 lines · 51 tokens per session scan A 32cf2ba0a4fa
judge-bug-hunter is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 2,085 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
project-check
Existing project health scan — audits Infrastructure, Security, Quality, and Harness setup. Read-only. Use when: '/project-check', 'project health check', 'project audit', 'what\'s missing', 'analyze my project', 'check setup'. Ends with /project-init and /setup recommendations. NOT for new projects (use…
full-audit
Exhaustive, denominator-driven audit of an entire area (codebase, docs, memory, skills, DB, config). Runs a 6-phase pipeline: scope agreement + prior-map diff -> deterministic sweep (counts/versions/paths/parsing plus cross-index reconciliation) -> parallel read-only content review (citations forced, rule dry-run) ->…