state-adjudicator

state-adjudicator is an agent for coding agents from nestharus/agent-implementation-skill. It costs 30 tokens per session (371 once invoked), scanned A, original, MIT.

A lightweight agent that classifies another agent’s output into a known state, such as aligned, problematic, underspecified, completed, or blocked by a dependency. It returns the state as structured JSON.

In plain words
What is it for?
Use it to interpret review, implementation, or coordination results and route the next workflow action.
Why use it?
It resolves ambiguous output when simple pattern matching cannot determine what happened. This gives the workflow a consistent status to act on.

Agent

Install

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.

agentmods
npx agentmods add agents/nestharus/agent-implementation-skill/state-adjudicator
Clone the repo
git clone --depth 1 https://github.com/nestharus/agent-implementation-skill

Wrote 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.

agentmods badge for state-adjudicator

README.md
[![agentmods](https://agentmods.dev/badge/agents/nestharus/agent-implementation-skill/state-adjudicator.svg)](https://agentmods.dev/agents/nestharus/agent-implementation-skill/state-adjudicator)
Your own site
<a href="https://agentmods.dev/agents/nestharus/agent-implementation-skill/state-adjudicator"><img src="https://agentmods.dev/badge/agents/nestharus/agent-implementation-skill/state-adjudicator.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 371 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.00371
Opus 5 $0.00015 $0.00186
Sonnet 5 $0.00006 $0.00074
Haiku 4.5 $0.00003 $0.00037

Measured yesterday against content hash c81471e0ff85, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

state-adjudicator 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 yesterday.

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.

src/staleness/agents/state-adjudicator.md · 56 lines

What it actually says

State Adjudicator

You classify agent output into exactly one state. This is a classification task — do NOT modify files, do NOT run implementations, do NOT explore. Just read and classify.

Input

You receive:

  1. The agent's output file path
  2. The expected output states for that agent type

Classification

Read the output file. Determine which state the output represents:

  • ALIGNED — The agent found no problems. Everything is coherent.
  • PROBLEMS — The agent found specific issues that need fixing.
  • UNDERSPECIFIED — The agent cannot proceed because information is missing. It needs human input or upstream decisions.
  • NEED_DECISION — The agent encountered a fork requiring human choice between alternatives.
  • DEPENDENCY — The agent is blocked on another section's output.
  • LOOP_DETECTED — The agent detected a cycle (same problems recurring).
  • COMPLETED — The agent finished its work successfully (no alignment judgment, just completion).

Output

Reply with EXACTLY one JSON block:

{
  "state": "ALIGNED",
  "detail": ""
}

Where state is one of the values above and detail is a brief explanation (empty string if not applicable). For PROBLEMS, include the problem text in detail.

If the output is garbled, empty, or truly unclassifiable, use:

{
  "state": "UNKNOWN",
  "detail": "brief explanation of why classification failed"
}
Changes

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.

  1. yesterday First seen · 56 lines · 30 tokens per session scan A c81471e0ff85

Subscribe to this mod's changes

state-adjudicator is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 371 once invoked, about $0.0002 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-09-03.

Related

Other agents, from other repositories

os-architect-tester

Validation agent for os-architect. Runs pre-scripted user scenarios through the os-architect interview flow via Copilot CLI, evaluates whether classification, routing, and HANDOFFBLOCK output meet acceptance criteria, and produces a structured test report. Use to battle-harden os-architect after changes, or to…

richfrem/agent-plugins-skills · 176 tokens

rlm-factory-init-agent

Guided setup wizard for the rlm-factory plugin. Works standalone (O(1) keyword search across dense file summaries, zero external deps) or as Phase 1 of a Super-RAG stack with vector-db and/or obsidian-wiki-engine. Starts with a setup mode question so the user gets exactly what they need. Creates rlmprofiles.json and…

richfrem/agent-plugins-skills · 247 tokens

vector-db-init-agent

Guided setup wizard for the vector-db plugin. Works standalone (semantic search with zero external dependencies) or as part of a Super-RAG stack with rlm-factory and/or obsidian-wiki-engine. Starts with a setup mode question so the user gets exactly what they need. Installs Python dependencies, creates…

richfrem/agent-plugins-skills · 179 tokens

requirements-doc-agent

Lightweight requirements documentation sub-agent modelled on the doc-coauthoring pattern. Dispatched by the exploration-cycle-orchestrator via Copilot CLI (cheap model, many invocations per session). Each invocation handles one focused capture task: problem framing, business requirements, user stories…

richfrem/agent-plugins-skills · 99 tokens

runtime-observer

Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.

richfrem/agent-plugins-skills · 56 tokens

debate-synthesizer

Multi-Agent Debate Judge. Receives two or more competing perspectives, proposals, or analyses and synthesizes them into a single hardened conclusion using dialectical reasoning. Resolves conflicts, names tradeoffs, and produces a final verdict.

richfrem/agent-plugins-skills · 52 tokens