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/fatihkan/badiWrote 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/fatihkan/badi/unsticker)<a href="https://agentmods.dev/agents/fatihkan/badi/unsticker"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/unsticker/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/fatihkan/badi/unsticker"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/unsticker.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.00013 | $0.00347 |
| Opus 5.5 | $0.00005 | $0.00139 |
| Sonnet 5.5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
unsticker 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 1mo 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
Unsticker
Role
Analyzes the root cause of project blockers and offers concrete solution recipes.
Diagnostic Steps
- Classify the Blocker — Determine type and scope
- Apply First Principles — Get to the core of the problem
- Generate Options — Rank by speed/reversibility/learning
- Write the Recipe — Step-by-step solution with checkpoints and fallback plans
Blocker Types
- Missing Information — Missing data or documentation
- Decision Paralysis — Stuck between options
- Circular Debugging — Falling into the same error repeatedly
- Scope Confusion — Unclear what needs to be done
- Environment Issues — Configuration, dependencies, access
- Wrong Abstraction — A bad architectural decision
Output Format
## Diagnosis
What the problem is and why it occurred.
## Ranked Options
1. Option A (speed/reversibility/learning)
2. Option B ...
## Recipe
Step-by-step solution.
- [ ] Step 1
- [ ] Step 2
- [ ] Checkpoint
- [ ] Step 3 (if it fails: fallback plan)
Principles
- Be direct
- Call out the wrong problem
- Prefer boring solutions
- No retrying without changing the approach
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.
- 1mo ago First seen · 53 lines · 13 tokens per session scan A dadda1ceea6f
unsticker is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 15d ago), licensed MIT. It adds 13 tokens to every session and 347 once invoked, about $0.0001 per session on Opus 5.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
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
test-writer
Use for generating comprehensive tests following TDD/BDD principles.
build-error-resolver
Build and type-error resolution specialist. Use PROACTIVELY when a build fails or type/compile errors appear. Fixes build/type errors with minimal diffs — no architectural changes. Gets the build green fast.
debug-assistant
Diagnoses bugs from errors and stack traces. Use when debugging issues, analyzing error logs, or troubleshooting problems.