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 randommonicle/claude-skills --skill reproduce-the-real-buildgit clone --depth 1 https://github.com/randommonicle/claude-skillsWrote 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/randommonicle/claude-skills/reproduce-the-real-build)<a href="https://agentmods.dev/skills/randommonicle/claude-skills/reproduce-the-real-build"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/reproduce-the-real-build/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/randommonicle/claude-skills/reproduce-the-real-build"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/reproduce-the-real-build.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.00097 | $0.00429 |
| Opus 5 | $0.00048 | $0.00215 |
| Sonnet 5 | $0.00019 | $0.00086 |
| Haiku 4.5 | $0.00010 | $0.00043 |
Grade A, and why
reproduce-the-real-build 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 12d 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.
What it actually says
Reproduce the real build
Two incidents, one shape: the environment that proved the change was not the environment
that ships it. A test using ESM-only syntax passed under the test runner and failed the
CommonJS production tsc, blocking the deploy. A build-toolchain upgrade left the lockfile
behind and kept working for two months only because both machines' node_modules had
drifted ahead of it — the first clean reinstall broke everything.
The rules
- Run the exact production build command locally before pushing anything the pipeline compiles — not just the test suite. The test runner tolerates what the release build rejects.
- Prove toolchain fixes from the tracked manifests alone:
npm ciinto a clean directory (nevernpm install, which mutates the lockfile and hides drift). A fix proven only on the machine that produced it has not been proven — that machine'snode_modulesis part of the experiment. - The lockfile describes what ships. If the build only works because installed
dependencies drifted ahead of it, the lockfile is silently wrong and the next
npm ciis the outage.
Why
Build environments drift invisibly toward working, and the drift is per-machine; only a manifest-only reconstruction tests what CI and the next machine will actually see. Evidence: ASH CLAUDE.md Railway/Docker tsc lesson (2026-05-20); ASH LESSONS_LEARNED 2026-07-19.
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.
- 12d ago First seen · 32 lines · 97 tokens per session scan A 5cc778548046
reproduce-the-real-build is a skill published in the GitHub repository randommonicle/claude-skills (23 stars, last pushed 6d ago), licensed Apache-2.0. It adds 97 tokens to every session and 429 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.