Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/shawnclybor/clybor-claude-toolingnpx agentmods add skills/shawnclybor/clybor-claude-tooling/build-evaluateWrote 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/skills/shawnclybor/clybor-claude-tooling/build-evaluate)<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/build-evaluate"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/build-evaluate/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/skills/shawnclybor/clybor-claude-tooling/build-evaluate"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/build-evaluate.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.00166 | $0.03238 |
| Opus 5.5 | $0.00066 | $0.01295 |
| Sonnet 5.5 | $0.00033 | $0.00648 |
| Haiku 4.5 | $0.00017 | $0.00324 |
Grade A, and why
build-evaluate 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 1mo 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Evaluate
Verify a build against its own definition of "done."
Phase 1: PARSE + PARALLEL LOAD
Batch in one message — independent reads:
Read.claude/PRPs/{slug}/prd.md,plan.md,state.jsonRead.claude/PRPs/_profiles/{type}.md(from PRD frontmatter)Glob.claude/PRPs/*/evaluate.md— for insight-promotion later, find prior similar builds for pattern matching
Verify:
state.jsonstateissuccessorstopped(notrunning) — refuse to evaluate a build still iterating- PRD has a concrete anchor case
- Plan has an acceptance test defined
If anchor case or acceptance test is missing: refuse and tell the user to update the PRD/plan first.
Phase 2: LOAD PROFILE
The profile may define:
- A canonical acceptance-test invocation (e.g.,
python3 scripts/validate-plugin.py path/to/plugin) - A fixture set the build must run against
- A specific reviewer agent to run as a final cold-read pass
Phase 3+4: RUN ACCEPTANCE TEST + ANCHOR CASE
⚠ SERIAL BY DEFAULT. Parallelize only where the write roots are certified disjoint. "Independent" does not mean "measures a different thing" — it means no two concurrently-running drivers WRITE the same tree. A driver that invokes a generator and then reads back what it generated is NOT independent of another driver doing the same: they interleave, and each asserts against a tree the other is rewriting. The run still prints PASS/FAIL, so the damage is invisible — the result is UNMEASURED, not failed, and unmeasured results that look green are how a build ships on evidence it never had.
Before launching anything, resolve each driver the plan names to (a) the generator it invokes and (b) the root that generator writes. Drivers sharing a root run ONE AT A TIME, in the order the plan lists them. Only drivers over disjoint fixtures run together, in one message.
- Acceptance test from the plan — serial across drivers sharing a write root
- Anchor case check (run the artifact against the PRD's one concrete example, compare output to expected outcome)
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.
- 1mo ago Changed · +27 lines · +8 tokens per session 41ee5b7ae963
- 1mo ago First seen · 223 lines · 158 tokens per session scan A 8d3c76ccd8d1
build-evaluate is a skill published in the GitHub repository shawnclybor/clybor-claude-tooling (6 stars, last pushed 5d ago), licensed MIT. It adds 166 tokens to every session and 3,238 once invoked, about $0.0007 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-09-05.
Other skills, from other repositories
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
quick
Execute an ad-hoc task with atomic commits. Skips full plan/review.
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
resume
Pick up where you left off. Restores context and suggests next action.
status
Show current project status and suggest what to do next.
config
Configure settings: depth, model profiles, features, git, and gates.