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/ProjectDXAI/labratWrote 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/projectdxai/labrat/why-stuck)<a href="https://agentmods.dev/commands/projectdxai/labrat/why-stuck"><img src="https://agentmods.dev/badge/commands/projectdxai/labrat/why-stuck/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/projectdxai/labrat/why-stuck"><img src="https://agentmods.dev/badge/commands/projectdxai/labrat/why-stuck.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.00000 | $0.00164 |
| Opus 5.5 | $0.00000 | $0.00066 |
| Sonnet 5.5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
why-stuck 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
Diagnose why the frontier is not moving.
- Run
python scripts/operator_helper.py status. - Read
state/frontier.json, focusing onfamily_fundingcredits,plateau_counter,frame_break_required, andaudit_queue. - Read the last five entries in
state/evaluations.jsonl. Note the distribution offailure_classvalues. - Read the last five entries in
state/candidates.jsonl. Note which families are spending credits without promoting. - Summarize in one paragraph:
- which family is blocking,
- what the dominant recent failure class is,
- whether the next step is audit, more mutations, or frame break.
Do not write any durable files. The goal here is situational awareness, not new state.
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 · 13 lines · 0 tokens per session scan A 6113018ac412
why-stuck is a command published in the GitHub repository ProjectDXAI/labrat (237 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 164 tokens. 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-30.
Other commands, from other repositories
report-bug
Report a bug in the Lavra plugin.
yolo-abort
Immediate halt of /yolo Hive session mid-action — partial state saved, in-flight git operations rolled back where possible, audit log finalized with abort flag.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Asks before pushing and creating a PR; --no-pr commits locally without asking.
loop-execution-evaluator
Verify implementation quality. Evaluate-Loop Step 4.
code-quality
Code review and bug prediction — find quality issues, style violations, and likely bugs.
fix-test
Auto-diagnose and fix failing tests — identifies root causes and applies fixes.