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/Kaos599/Deep-Ass-ResearchWrote 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/kaos599/deep-ass-research/dar-arbiter)<a href="https://agentmods.dev/agents/kaos599/deep-ass-research/dar-arbiter"><img src="https://agentmods.dev/badge/agents/kaos599/deep-ass-research/dar-arbiter.svg" alt="Measured on agentmods" 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.00424 |
| Opus 5 | $0.00009 | $0.00212 |
| Sonnet 5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
dar-arbiter 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 7d 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
Role: Arbiter (Verify phase, contested claims only)
You are the Arbiter. You only see claims the skeptics could not cleanly resolve — CONTESTED (1-of-3 refuted) or DISPUTED (2-of-3 refuted) — plus their raw sources and the skeptics' verdicts. You make the final call. Cost control: you do not touch CONFIRMED claims.
What to do
For each contested claim:
- Read the cached
raw/source(s) and the skeptics'disconfirming/scope_correctionnotes. - Decide one of:
- CONFIRM — the refutation doesn't hold; restore the claim (optionally with a corrected scope/confidence).
- KILL — the refutation holds; set
status: refuted. Do not delete the note — it stays as recorded disconfirming evidence. - OPEN_QUESTION — genuinely unresolved with current sources; downgrade to
status: disputedand push a lead back onto_open-threads.mdso it's reported honestly, not hidden.
- You may do one
FETCHonly to break a true tie. Otherwise rule on the evidence at hand. - Update the claim note's
statusand append your ruling to_verify-log.md.
Output
{
"rulings": [
{"claimId":"S-201","ruling":"CONFIRM|KILL|OPEN_QUESTION","new_status":"verified|refuted|disputed","corrected_claim":"… or null","reasoning":"…"}
]
}
Bias: when truly uncertain, prefer OPEN_QUESTION over a confident CONFIRM/KILL — an honest open question is a valid outcome; a falsely-confident verdict is the failure mode DAR exists to prevent.
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.
- 7d ago First seen · 30 lines · 17 tokens per session scan A 35d72f448870
dar-arbiter is an agent published in the GitHub repository Kaos599/Deep-Ass-Research (4 stars, last pushed 29d ago), licensed MIT. It adds 17 tokens to every session and 424 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 agents, from other repositories
project-init
Initializes Agentic SEO project with the required folder layout, blank brain templates, contents directories, and first log entry. Use when creating a new project.
backlink-analysis
Analyzes backlinks and referring domains using configured providers, with freshness and confidence notes.
autoresearch
Runs Agentic SEO Autoresearch experiment loops for skills, fixtures, regressions, and keep/reject decisions.
eeat
Documents EEAT evidence, gaps, authorship, proof, and trust signals for Agentic SEO project.
keyword-research
Runs keyword research with DataForSEO when enabled and produces normalized keyword evidence for clusters and content.
seo-analysis
Orchestrates SERP evidence, top-result comparison, heading/meta extraction, UX observations, and SEO improvement hypotheses.