smoke-test-issue

smoke-test-issue is a skill for Claude Code from loopdive/js2. It costs 32 tokens per session (409 once invoked), scanned A, original, Apache-2.0.

A quick check that compiles and runs sample tests from an issue against the current main branch. Main is the repository's primary shared branch.

In plain words
What is it for?
Use it before assigning an issue to test two or three sample files and decide whether the issue is still failing, already fixed, or only partly fixed.
Why use it?
It prevents developers from spending time on bugs that have already been fixed and distinguishes real failures from resolved ones.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it before assigning an issue to test two or three sample files and decide whether the issue is still failing, already fixed, or only partly fixed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/loopdive/js2/smoke-test-issue
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 loopdive/js2 --skill smoke-test-issue
Clone the repo
git clone --depth 1 https://github.com/loopdive/js2

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 smoke-test-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/loopdive/js2/smoke-test-issue/github.svg)](https://agentmods.dev/skills/loopdive/js2/smoke-test-issue)
Your own site
<a href="https://agentmods.dev/skills/loopdive/js2/smoke-test-issue"><img src="https://agentmods.dev/badge/skills/loopdive/js2/smoke-test-issue/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 smoke-test-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/loopdive/js2/smoke-test-issue"><img src="https://agentmods.dev/badge/skills/loopdive/js2/smoke-test-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 409 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 21
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
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.00032 $0.00409
Opus 5.5 $0.00013 $0.00164
Sonnet 5.5 $0.00006 $0.00082
Haiku 4.5 $0.00003 $0.00041

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

Security

Grade A, and why

smoke-test-issue 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/smoke-test-issue/SKILL.md · 46 lines

What it actually says

Smoke Test Issue

Validates whether an issue's sample test cases still fail against current main.

Usage

Provide the issue number. This skill reads the issue file and compiles 2-3 sample tests.

Steps

  1. Read the issue file at plan/issues/{N}.md
  2. Find the "Sample files" section — extract 2-3 test file paths
  3. For each sample test, compile and run:
npx tsx -e "
import {compile} from './src/index.ts';
import {readFileSync} from 'fs';
import {parseMeta, wrapTest} from './tests/test262-runner.ts';
import {buildImports} from './src/runtime.ts';
const src = readFileSync('test262/test/[TEST_FILE]','utf-8');
const meta = parseMeta(src);
const {source:w} = wrapTest(src,meta);
const r = compile(w, {fileName:'test.ts'});
if (!r.success) { console.log('CE:', r.errors[0]?.message); process.exit(1); }
const imports = buildImports(r.imports, undefined, r.stringPool);
const {instance} = await WebAssembly.instantiate(r.binary, imports);
const ret = instance.exports.test();
console.log('Result:', ret === 1 ? 'PASS' : 'FAIL (returned ' + ret + ')');
"
  1. Report results:
    • All fail: issue is real, ready to dispatch
    • All pass: issue is already fixed — close it, mark it done
    • Mixed: issue is partially fixed — update the issue with current status

Output

Message with: "Smoke test #N: [REAL|FIXED|PARTIAL] — [details]"

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 First seen · 46 lines · 32 tokens per session scan A 962428affa59

Subscribe to this mod's changes

smoke-test-issue is a skill published in the GitHub repository loopdive/js2 (67 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 409 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

migrate-oxlint

Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.

oxc-project/oxc · 44 tokens

insta-snapshots

Review and update Oxc Insta snapshots non-interactively after expected output changes or snapshot test failures.

oxc-project/oxc · 25 tokens

fixing-flaky-tests

Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when hogli ci:insights or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a…

PostHog/posthog · 220 tokens

test-electron-app

Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…

PostHog/posthog · 112 tokens

extending-hobby-smoke-tests

Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml. Use when adding an ingestion round trip, deciding whether a product belongs in Hobby CI, changing the CI Hobby service topology or API-key scopes, or diagnosing a smoke test that captures data…

PostHog/posthog · 83 tokens

extending-personhog-test-harness

When and how to add scenarios, chaos events, and invariants to the personhog e2e test harness (rust/personhog-test-harness). Use after fixing a bug or regression in the personhog leader path (leader, router, writer, replica, coordination protocol) so the fix gets a permanent regression scenario; when adding a new…

PostHog/posthog · 134 tokens