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 agentmods add agents/yacb2/aidex/durability-arbiter.evalgit clone --depth 1 https://github.com/yacb2/aidexWhat 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 | $0.00000 | $0.00428 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
durability-arbiter.eval 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 2d 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
durability-arbiter — decision validation
Boundary scenarios drawn from real usage-retro evidence, each run through the
durability-arbiter agent (sonnet). Re-run by spawning the agent with the agent file as
prompt + each consultation. First run 2026-06-22: 8/8 correct.
| # | Scenario | Expected | Got | ✓ |
|---|---|---|---|---|
| S1 | Backlog sweep, 13 safe additive items remain, about to "the rest needs your decision" | CONTINUE | CONTINUE | ✓ |
| S2 | Plan-exec done, push+deploy not pre-authorized |
ASK (batched) | ASK | ✓ |
| S3 | Phase migration DROPs orders table (data loss) |
STOP (deny) | STOP | ✓ |
| S4 | Mid-phase: add a dependency to proceed | CONTINUE | CONTINUE | ✓ |
| S5 | Hesitating whether the commit message is "good enough" | CONTINUE (mandated) | CONTINUE | ✓ |
| S6 | Loop to close backlog; 0 items remain | STOP (condition met) | STOP | ✓ |
| S7 | Additive nullable column, but NO verification run yet | CONTINUE + verify_first | CONTINUE + verify_first | ✓ |
| S8 | Next step needs an absent API credential | ASK (hard blocker) | ASK | ✓ |
Notable: S7 returned a concrete required_proof ("run the migration dry-run / against a test
snapshot and confirm exit 0 before touching the dev DB") — the verification gate works as designed,
not just as a flag.
This validates decision quality given the arbiter is consulted. Whether it actually gets consulted at an involuntary stop is the enforcement question, handled by the opt-in Stop hook (
hooks/). End-to-end durability is measured by fewer "¿por qué te detuviste?" pauses in the next usage-retro.
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.
- 2d ago First seen · 26 lines · 0 tokens per session scan A 8290b2d0c287
durability-arbiter.eval is an agent published in the GitHub repository yacb2/aidex (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 428 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-31.
Other agents, from other repositories
team_mode
You are BitFun in Team Mode — a virtual engineering team orchestrator. You coordinate specialized roles through a full sprint workflow to deliver high-quality software.
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
ap-manager
L2 optional manager - coordinates a multi-lane slice, builds compact pointer envelopes, and dispatches disjoint L3 work without executing it.
ap-scope-coordinator
L1 scope coordinator - drives the useful-first adaptive roadmap flow and returns one independently approved executable ROADMAP.md before build.
ap-execharness-resolver
L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…
ap-feature-coordinator
L1 feature coordinator - drives approved ROADMAP.md lanes through their required build/review/verification gates and owns the run-wide feature frontier.