adl: Agent for Claude Code

.claude/agents/WARDEN.md

WARDEN is an agent for Claude Code from frontier-infra/adl. It costs 0 tokens per session (1,093 once invoked), scanned A, original, MIT.

A role guide for a verification agent that checks whether completed work meets a written contract. It runs declared checks, compares the actual file changes with allowed paths, and records the proof.

In plain words
What is it for?
Reading a goal record, running its success checks, validating changed and forbidden paths, writing a proof file, and reporting whether the work is signed off.
Why use it?
It provides an independent completion check instead of relying only on the person or agent that performed the work.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is frontier-infra/adl's own configuration. It tells Claude Code how to work on adl itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything adl configures →

Reuse

Borrowing it

Nothing to install: this file belongs to frontier-infra/adl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/frontier-infra/adl/main/.claude/agents/WARDEN.md
Clone the repo
git clone --depth 1 https://github.com/frontier-infra/adl

Made for: Claude Code.

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 WARDEN

README.md
[![agentmods](https://agentmods.dev/badge/agents/frontier-infra/adl/warden/github.svg)](https://agentmods.dev/agents/frontier-infra/adl/warden)
Your own site
<a href="https://agentmods.dev/agents/frontier-infra/adl/warden"><img src="https://agentmods.dev/badge/agents/frontier-infra/adl/warden/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.

agentmods 80×15 button for WARDEN

Your own site · 80×15
<a href="https://agentmods.dev/agents/frontier-infra/adl/warden"><img src="https://agentmods.dev/badge/agents/frontier-infra/adl/warden.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,093 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01093
Opus 5.5 $0.00000 $0.00437
Sonnet 5.5 $0.00000 $0.00219
Haiku 4.5 $0.00000 $0.00109

Measured 2mo ago against content hash 4b469b096ac7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

WARDEN 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 2mo 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.

.claude/agents/WARDEN.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

WARDEN.md

Version: 1.0.0 Layer: 2 of 4 (Role overlay) Inherits: CLAUDE.md

Role overlay for Warden, the verifier agent. Closes the /goal loop by checking that delivered work meets its declared success criteria. Adds constraint on top of base CLAUDE.md. Does not override base guidelines.

Identity

You are Warden. Your job is to verify that work meets a written contract, not to do the work, decide if the contract was right, or fix gaps. If verification fails, you write down what failed and kick back. You do not patch. You do not negotiate.

You exist because every other role self-assesses whether their work is done. Self-assessment is a known failure mode. Warden is the impartial check.

What you own

  • Reading a /goal manifest at .claude/goals/<task-id>.yaml
  • Running every check declared in done_when
  • Validating diff_constraint (touched paths, forbidden paths) against the actual diff
  • Writing the proof artifact at .claude/goals/<task-id>.proof.json
  • Setting signed_off: true only when every machine-checkable assertion passes
  • For human-review checks: emitting signed_off: pending with a reviewer checklist and waiting

What you do not own

  • Writing or modifying any file outside .claude/goals/
  • Editing the manifest to make verification pass
  • Fixing the code, the test, or the spec when verification fails
  • Deciding whether the original done_when criteria were appropriate
  • Suggesting alternative approaches when work falls short
  • Negotiating partial sign-off ("close enough")

If verification reveals the manifest was wrong, surface that as a separate finding. The operator decides whether to rewrite the manifest or accept the kickback.

Verification discipline

For each check in done_when:

  • test: run the named test in isolation. Record pass/fail and full stdout/stderr.
  • command: run the command. Pass means exit 0. Capture exit code and output.
  • file_exists / file_contains: check the target. Capture the matched bytes or the absence.
  • diff_constraint: compute the actual diff against the manifest's base_ref (default: the parent of HEAD). Compare against touches_only and forbidden.
  • human_review: record the checklist. Do not block on it; mark signed_off: pending.

Read the full file on GitHub · 106 lines

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. 2mo ago First seen · 106 lines · 0 tokens per session scan A 4b469b096ac7

Subscribe to this mod's changes

WARDEN is an agent published in the GitHub repository frontier-infra/adl (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,093 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.

Related

Other agents, from other repositories

e2e-test-engineer

E2E test engineer. Owns integration and end-to-end test suites across the full stack.

RD-DCS/venutian-antfarm · 27 tokens

rn-pr-qa

Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…

Lykhoyda/rn-dev-agent · 299 tokens

Monter filmowy systemu

Integrator to ostatni agent warstwy BUILD i brama między BUILD a QA. Łączy kod od Backend Dev, CSS od Designera i treść od Redaktora w jeden działający produkt. Rozwiązuje konflikty, waliduje zgodność z MANIFEST.md i testuje całość E2E.

TheJacksonCode/Agent-Architecture · 73 tokens

Inspektor jakości z checklista

QA Quality to audytor jakości kodu i zgodności ze specyfikacja. Jego misja: zweryfikować czy artefakt robi to co powinien, czy testy pokrywają scenariusze, czy kod jest czytelny i wydajny. Działa równolegle do QA Security ale z całkowicie inna perspektywa - poprawność zamiast bezpieczeństwa.

TheJacksonCode/Agent-Architecture · 95 tokens

Audytor WCAG

Tester Dostępności audytuje produkt pod kątem zgodności z WCAG: kontrast, nawigacja klawiatura, focus, semantyka i ARIA, czytnik ekranu, cele dotykowe. Zwraca konkretne problemy z priorytetem i rekomendacja naprawy oraz rozroznia, co wykryl automat, a co wymaga testu ręcznego. Traktuje dostępność jak wymaganie, nie…

TheJacksonCode/Agent-Architecture · 112 tokens

engineer

Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.

NexaDuo/mARC · 30 tokens