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/VoxTechnologies/transmute-frameworknpx agentmods add skills/voxtechnologies/transmute-framework/smokeWrote 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/voxtechnologies/transmute-framework/smoke)<a href="https://agentmods.dev/skills/voxtechnologies/transmute-framework/smoke"><img src="https://agentmods.dev/badge/skills/voxtechnologies/transmute-framework/smoke.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.00094 | $0.02571 |
| Opus 5 | $0.00047 | $0.01286 |
| Sonnet 5 | $0.00019 | $0.00514 |
| Haiku 4.5 | $0.00009 | $0.00257 |
Grade A, and why
smoke scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Verify the production URL is accessible and responding. Check with `curl -sI <production-url> | head -1` (expect HTTP 200 or 301/302). If unreachable, STOP and verify deployment status. How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Smoke Verification — Stage 7V
Read the detailed guide at ${CLAUDE_SKILL_ROOT}/references/smoke-detailed-guide.md for the full verification checklist, report template, known failure patterns, and rollback guidance. Read ${CLAUDE_SKILL_ROOT}/references/feature-scenario-generation.md for the scenario generation algorithm.
Prerequisites
- Verify the production URL is accessible and responding. Check with
curl -sI <production-url> | head -1(expect HTTP 200 or 301/302). If unreachable, STOP and verify deployment status. - Check
./plancasting/_launch/readiness-report.mdexists. If it shows FAIL, stop and report the blocker. If READY or CONDITIONAL PASS with documented minor issues, proceed. If it does not exist, proceed but note in the report: "Stage 6H pre-launch verification was not completed." - If 6R was run, verify
./plancasting/_audits/runtime-remediation/report.mdshows PASS or CONDITIONAL PASS. If FAIL, STOP — 6R must pass before Stage 7. - Verify
./plancasting/_audits/visual-verification/report.mdor./plancasting/_audits/visual-polish/report.mdexists. Warn if neither is found. - Verify scenario generation file exists:
./plancasting/transmute-framework/feature_scenario_generation.md. If missing, copy from the Transmute Framework Template directory. See CLAUDE.md § "Pre-6V Setup" for copy instructions. - Create output directories:
mkdir -p ./plancasting/_audits/production-smoke mkdir -p ./screenshots/production - Read
CLAUDE.md,plancasting/tech-stack.md, and checkplancasting/tech-stack.mdfor theSession Languagesetting. Generate all reports in the specified language.
Inputs
- Production URL: The live application URL
- Scenario Generation Guide:
${CLAUDE_SKILL_ROOT}/references/feature-scenario-generation.md(if not available, use PRD files directly) - 6V Scenario Matrix (if exists):
./plancasting/_audits/visual-verification/feature-scenario-matrix.md - 6V Report:
./plancasting/_audits/visual-verification/report.md - 6R Report (if exists):
./plancasting/_audits/runtime-remediation/report.md - 6P/6P-R Report (if exists):
./plancasting/_audits/visual-polish/report.md - PRD files:
./plancasting/prd/02-feature-map-and-prioritization.md,04-epics-and-user-stories.md,06-user-flows.md,07-information-architecture.md,08-screen-specifications.md - Tech Stack:
./plancasting/tech-stack.md - E2E Config:
./playwright.config.ts,./e2e/constants.ts
What ships with it
2 files 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.
- 7d ago First seen · 130 lines · 94 tokens per session scan A e2fa1e736962
smoke is a skill published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 2,571 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
playwright
Browser automation and end-to-end testing with Playwright. Use when building/testing frontends, automating user workflows, taking screenshots, validating UI state, filling forms, testing across browsers, or mentions "playwright", "E2E test", "browser automation", "screenshot".
enterprise-test-suites
Comprehensive testing matrix spanning Unit, Integration, E2E (Playwright), Contract (Pact), Chaos/Fault-Injection, Mutation, Load/Stress (k6), and Security Fuzz testing.
e2e-fix-cycle
Automated E2E test-fix cycle. Runs tests, analyzes failures, applies fixes in batches, re-runs until pass. Use for full automation: 'fix e2e', 'e2e cycle', 'auto-fix tests'.
e2e-run
Smart E2E test runner with auto-detection of Playwright project and wait strategies. Use when running E2E tests: 'run e2e', 'e2e admin', 'test admin-tests', 'run creator tests'.
playwright-for-android
End-to-end Android debug loop on an emulator. Builds the APK with a Gradle task, boots a named AVD, installs and launches the target package, then drives a single feature via adb-injected UI actions while capturing a unified logcat-and-actions timeline plus a developer-facing test report. Use when the user wants to…
sap-test-replay
Turns a recorded business scenario into a re-runnable pass/fail GUI regression test — the eCATT/CBTA equivalent the suite lacks — so a regression cycle stops meaning "re-test transactions by hand and paste screenshots into Word". A scaffold-recorded linear scenario (control IDs + screen identity + popup transitions…