build-execute

build-execute is a skill for Claude Code from shawnclybor/clybor-claude-tooling. It costs 194 tokens per session (4,466 once invoked), scanned A, original, MIT.

A bounded loop that follows a validated build plan, checks the result, and applies edits within stated limits. It can run an adversarial review for certain contract or behavior changes.

In plain words
What is it for?
It helps carry out planned build changes, review selected risky changes, and measure each iteration.
Why use it?
The limits help prevent repeated edits or execution from continuing without control, including where spending may apply.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

Good fit It helps carry out planned build changes, review selected risky changes, and measure each iteration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shawnclybor/clybor-claude-tooling/build-execute
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.

Any agent
npx skills add shawnclybor/clybor-claude-tooling --skill build-execute
Clone the repo
git clone --depth 1 https://github.com/shawnclybor/clybor-claude-tooling

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 build-execute

README.md
[![agentmods](https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/build-execute/github.svg)](https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/build-execute)
Your own site
<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/build-execute"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/build-execute/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 build-execute

Your own site · 80×15
<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/build-execute"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/build-execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 194 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,466 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.00194 $0.04466
Opus 5.5 $0.00078 $0.01786
Sonnet 5.5 $0.00039 $0.00893
Haiku 4.5 $0.00019 $0.00447

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

Security

Grade A, and why

build-execute 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.

.claude/skills/build-execute/SKILL.md · 331 lines

How it starts

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

Build Execute

Bounded execution loop. The scheduler and budgeter; per-iteration work is delegated.

Hard preconditions (REFUSE if unmet)

  • .claude/PRPs/{slug}/prd.md exists
  • .claude/PRPs/{slug}/plan.md exists
  • bash .claude/PRPs/{slug}/probes/run.sh re-run in THIS session: 0 MISMATCH, 0 source changed
  • check-plan-soundness.py {slug}/plan.md --prd {slug}/prd.md exits 0
  • Stage 3 disposition is RECORDED in state.json as validate_regime and is one of the three below
  • Profile's hard preconditions (defined in the profile) are met
  • No prior .claude/PRPs/{slug}/state.json is in state: running (refuse double-runs)

If any precondition fails: stop, list the failures, do nothing else.

The three Stage 3 dispositions

Premises get reviewed once — confirmed, contradicted, or decided. None of those improves by re-reviewing, so "validate again until PASS" is not a thing. Record exactly one:

validate_regime When Must also record
PASS Panel ran, frame held Date, which premises were contested
SKIPPED Nothing contested — no new module, no schema change, no reversal of what a field MEANS. The common case on a running build Suite green, mutations FULL PASS, driver written RED first
WAIVED Panel ran, FAILED, owner overrode on the record Who, when, why, substituted gate, and what_is_NOT_claimed

⚠ SKIPPED needs a mutation-proven suite. Green but unmutated is unfalsifiable — that reverts the target to greenfield, which takes the panel. So does a schema change or a new module, whatever the surrounding suite proves.

⚠ Three FAILs on one target is a process defect (Hard Rule 9). Re-scope; don't convert a repeated FAIL into a waiver.

Hard caps (defaults — overridable per invocation but not per iteration)

  • Max iterations: 3 (override --max-iterations N)
  • Max edits per iteration: defined by profile (e.g., skill = 1 file, plugin = N skills × 1 file each)
  • Max spend: profile-defined. Skip if profile has no spend (most internal builds have none)
  • Stagnation: 2 consecutive iterations with no measurable progress on the acceptance test → stop automatically

Read the full file on GitHub · 331 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. 1mo ago Changed · +8 lines b9e956bf52cf
  2. 2mo ago First seen · 323 lines · 194 tokens per session scan A 6aea49b2504f

Subscribe to this mod's changes

build-execute is a skill published in the GitHub repository shawnclybor/clybor-claude-tooling (6 stars, last pushed yesterday), licensed MIT. It adds 194 tokens to every session and 4,466 once invoked, about $0.0008 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.

Related

build-execute compared with skills from other repositories

build-execute next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
build-executeshawnclybor/clybor-claude-toolingSkill6yesterdayMITA194Claude Code
autonomousSienkLogic/plan-build-runSkill187mo agoMITA20Claude Code
quickSienkLogic/plan-build-runSkill187mo agoMITA19Claude Code
auditSienkLogic/plan-build-runSkill187mo agoMITA16Claude Code
debugSienkLogic/plan-build-runSkill187mo agoMITA13Claude Code
exploreSienkLogic/plan-build-runSkill187mo agoMITA18Claude Code
resumeSienkLogic/plan-build-runSkill187mo agoMITA17Claude Code