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 agentmods add skills/experientiallabs/experiential/test-buildnpx skills add experientiallabs/experiential --skill test-buildgit clone --depth 1 https://github.com/experientiallabs/experientialWrote 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/experientiallabs/experiential/test-build)<a href="https://agentmods.dev/skills/experientiallabs/experiential/test-build"><img src="https://agentmods.dev/badge/skills/experientiallabs/experiential/test-build.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 | $0.00076 | $0.04539 |
| Opus 5 | $0.00038 | $0.02269 |
| Sonnet 5 | $0.00015 | $0.00908 |
| Haiku 4.5 | $0.00008 | $0.00454 |
Grade C, and why
test-build scanned grade C with 2 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$WORK" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sSL --fail -H "Authorization: Bearer $HF_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test the build path
Execute the current CLI path on one isolated local root. This is a live provider run, not the deterministic fixture test. It proves the commands complete, that the fitted router replays exactly, and that routed loopback traffic journals durably. It does not claim router quality.
Every step is an exp or standard shell command. Do not edit models.toml, project files, or
artifacts by hand. Do not call internal Python APIs. If a step cannot be done through the CLI,
stop and report the UX gap.
Do not use OpenRouter. Do not run exp optimize model. Do not start E2B sandboxes. Do not commit
.exp/, traces, or any generated artifact.
Time every numbered step and report the table at the end.
Fit dataset
This skill fits the pinned public terminal-tasks export by default. A caller may override any variable below; when overriding, the caller owns the digest. Record the effective values in the final report so the fitted dataset is unambiguous.
EXP_TEST_BUILD_PROJECT(defaultterminal-tasks): local project ID passed to every commandEXP_TEST_BUILD_TRACES(default$HOME/exp-fixtures/terminal-tasks-traces.otel.jsonl): local trace-export fileEXP_TEST_BUILD_TRACES_SHA256(default21c62cba7e3372cbf03df051dc2408699fbf8ea3561ba661b599e4949f0e5d42): lowercase hex digestEXP_TEST_BUILD_SOURCE(defaultotlp): trace source format
When the default file is absent, download the pinned export once with HF_TOKEN:
https://huggingface.co/datasets/experiential-labs/wmo-terminal-tasks-traces/resolve/540883e451dc13d34fb50fdd36b143cb0f1fb0db/traces.otel.jsonl
Do not skip the digest check. If the file is absent and cannot be downloaded, or the digest does not match, stop.
Optional work root: EXP_TEST_BUILD_ROOT (default /tmp/exp-test-build). Keep the trace file
outside that directory. The skill deletes the work root at the start of the run.
Secrets
Fail before any write if a required variable is missing or empty. Never print a secret value.
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.
- 5d ago First seen · 357 lines · 76 tokens per session scan C a53bd7c269cd
test-build is a skill published in the GitHub repository experientiallabs/experiential (849 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 4,539 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…