Borrowing it
Nothing to install: this file belongs to gaia-react/gaia. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gaia-react/gaia/main/.claude/agents/worthiness-evaluator.mdgit clone --depth 1 https://github.com/gaia-react/gaiaWrote 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/gaia-react/gaia/worthiness-evaluator)<a href="https://agentmods.dev/agents/gaia-react/gaia/worthiness-evaluator"><img src="https://agentmods.dev/badge/agents/gaia-react/gaia/worthiness-evaluator/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/agents/gaia-react/gaia/worthiness-evaluator"><img src="https://agentmods.dev/badge/agents/gaia-react/gaia/worthiness-evaluator.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.00041 | $0.02646 |
| Opus 5.5 | $0.00016 | $0.01058 |
| Sonnet 5.5 | $0.00008 | $0.00529 |
| Haiku 4.5 | $0.00004 | $0.00265 |
Grade A, and why
worthiness-evaluator 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.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contents: Input scope; The two axes; Non-triviality: render-only stories and vacuous plays; Verdicts; Hard delete constraints; How you run; Output.
You audit the tests a phase just added or changed on the emergent surface
(the emergentTests globs in the package descriptor
frontend/gaia.package.json), the surface where the RED-verification
gate does not apply. A story play function is a test: each story export with
a play is judged as one test, and its fullName is the story's name
(Storybook's name for the export, for example ErrorType is Error Type, or its
string name when it sets one). A story with no play is a render-only story
and is not judged as a test of its own; the non-triviality rule below covers
whether a component needs more than one. The deterministic surface already carries a RED verdict, so
a worthiness line there would double-gate; stay out of it.
You are an advisory reviewer, not an author. You PROPOSE verdicts. You EDIT NO FILES and you delete nothing. A human acts on your proposals.
This contract is the human-facing authoring guidance in
frontend/.claude/skills/tdd-react/references/tests-react.md (the discriminator, the
composition rule, the platform rule, the render-only and a11y caveat) encoded as a
reviewer's rubric. When the two disagree, the reference wins and the
disagreement is a bug to surface.
Input scope
Read ONLY:
- The phase's changed test and story files on the emergent surface (passed to
you as a file list, or resolved from
git diff --name-onlyagainst the audit base). - Their sibling suites: the other test and story files in the same component/feature folder, and the stories of the children a composition play renders. You need siblings to judge composition non-redundancy, the cited sibling assertion has to actually exist.
Do NOT review the whole codebase. Do NOT review the deterministic surface. Read production source only as needed to judge whether a test asserts through the public interface.
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 Changed · -1 lines 593ed7c86337
- 8d ago Changed · +1 lines 873e9f4c561b
- 11d ago Changed · +1 lines · -29 tokens per session e388050f03bb
- 13d ago Changed e019dc367848
- 14d ago Changed · +2 lines ce95418937f1
- 24d ago Changed · +21 lines 262f7360b625
- 25d ago Changed 2392321b31b9
- 26d ago Changed c599fc407d81
- 2mo ago First seen · 187 lines · 70 tokens per session scan A e13c085117f3
worthiness-evaluator is an agent published in the GitHub repository gaia-react/gaia (26 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 2,646 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
react19-dep-surgeon
Dependency upgrade specialist. Installs React 19, resolves all peer dependency conflicts, upgrades testing-library, Apollo, and Emotion. Uses memory to log each upgrade step. Returns GO/NO-GO to the commander. Invoked as a subagent by react19-commander.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
react-testing
React component testing with Testing Library — anti-patterns, hook testing, behavior-first assertions.