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.
npx skills add closedloop-ai/claude-plugins --skill build-status-cachegit clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWrote 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/closedloop-ai/claude-plugins/build-status-cache)<a href="https://agentmods.dev/skills/closedloop-ai/claude-plugins/build-status-cache"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/build-status-cache.svg" alt="Measured on agentmods" 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.00069 | $0.00396 |
| Opus 5 | $0.00034 | $0.00198 |
| Sonnet 5 | $0.00014 | $0.00079 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
build-status-cache 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.
What it actually says
Build Status Cache
Check whether a Phase 7 build-validator launch can be skipped because no code has changed since Phase 5 build validation passed.
When to Use
- After Phase 5 build passes: Stamp the cache
- At Phase 7 build check: Check the cache before launching build-validator
Usage
Stamp (after Phase 5 build passes)
bash ${CLAUDE_SKILL_DIR}/scripts/check_build_cache.sh <WORKDIR> stamp
Output: BUILD_CACHE_STAMPED
Check (before Phase 7 build)
bash ${CLAUDE_SKILL_DIR}/scripts/check_build_cache.sh <WORKDIR>
Interpreting Output
Cache Hit
BUILD_CACHE_HIT
Action: Skip the Phase 7 build-validator launch. Build was already validated and no code changed.
Cache Miss
BUILD_CACHE_MISS
reason: <why the cache is stale or missing>
Action: Run build-validator as normal.
How It Works
The script hashes git diff HEAD output (all uncommitted changes). After Phase 5 passes, this hash is stored. Before Phase 7 runs, the current hash is compared. If Phase 6 (visual QA) made code fixes, the hash changes and build-validator re-runs. If Phase 6 was skipped or made no code changes, the hash matches and build-validator is skipped.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 59 lines · 69 tokens per session scan A 7c756541d644
build-status-cache is a skill published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 396 once invoked, about $0.0003 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-07.
Other skills, from other repositories
auto-optimize
Autonomously optimize any Claude Code skill by running it repeatedly, scoring against binary evals, mutating the prompt, and keeping improvements. Use when: optimize/improve/benchmark/eval a skill, autoresearch, auto-optimize. Not for creating skills from scratch (use skill-creator-pro).
audit-harness
Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.
sd-plan-tests
The test-planning craft skill (software-delivery SDLC step 5). Run it AFTER front-authorization has frozen an atom's ACs and BEFORE implementation, to derive a per-AC test plan — happy / edge / negative cases plus the change-attributable baseline case for each pre-change checkpoint — mapped to the acceptance-contract…
mcp-tool-developer
Build Model Context Protocol (MCP) servers and tools from scratch. Full-stack MCP development with TypeScript/Python, testing, deployment, and registry publishing.
skill-test
Verifies that the skill system is working correctly.
id-simulate
The infra-delivery OFFLINE LOCAL-SIMULATION step (the new simulate step, between id-test and id-plan) — a PROCEDURE skill the generic agent runs ENTIRELY OFFLINE (no live cloud, no credentials) to author-and-prove the IaC corpus before the live pre-merge plan. Layer 1: apply the profile's EXISTING primitive OpenTofu…