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 mostafa-drz/claude-skills --skill smoke-testgit clone --depth 1 https://github.com/mostafa-drz/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/mostafa-drz/claude-skills/smoke-test)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/smoke-test"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/smoke-test/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/mostafa-drz/claude-skills/smoke-test"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/smoke-test.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.00051 | $0.01284 |
| Opus 5 | $0.00026 | $0.00642 |
| Sonnet 5 | $0.00010 | $0.00257 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
smoke-test 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 11d 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.
- **Be resourceful**: Use curl, gh, MCP tools, database CLIs, log files. How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smoke Test
Trace a resource, event, or feature through the system and verify it works end-to-end.
Preferences
Read ~/.claude/skills/smoke-test/preferences.md using the Read tool. If not found, no preferences are set.
Project context
On startup, use Bash to detect: CLAUDE.md presence, project stack files (ls package.json Cargo.toml pyproject.toml go.mod requirements.txt), and current git branch. Skip any that fail.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete~/.claude/skills/smoke-test/preferences.md, confirm, stop- anything else → run smoke test
Help
Smoke Test — Trace and verify something works end-to-end
Usage:
/smoke-test <natural language> Build and run a trace plan
/smoke-test config Set environment and verbosity defaults
/smoke-test reset Clear preferences
/smoke-test help This help
Examples:
/smoke-test uploaded a file to workspace 30 in prod, check the pipeline
/smoke-test verify login flow on staging
/smoke-test did my migration run correctly in production?
/smoke-test check webhook fires after order creation in dev
How it works:
1. Reads project context (CLAUDE.md, repo structure, APIs)
2. Builds a trace plan — ordered checks
3. Confirms the plan with you
4. Runs each check, reporting pass/fail
5. Summarizes with diagnosis
Current preferences:
(shown above under Preferences)
Config
Use AskUserQuestion:
Q1 — "Default environment?" (Production, Staging/Dev, Local, Ask each time (default)) Q2 — "Trace output verbosity?" (Concise, Detailed, Verbose on failure (default))
Save to ~/.claude/skills/smoke-test/preferences.md.
First-time detection
If no preferences file exists, show:
"First time using /smoke-test? Run /smoke-test config to set default environment and verbosity, or continue — I'll auto-detect."
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.
- 11d ago First seen · 183 lines · 51 tokens per session scan A 0cc58157f41b
smoke-test is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,284 once invoked, about $0.0003 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
shipkit-qa-visual
Visual QA using Playwright as a browser automation library. --setup installs Playwright and creates ui-goals.json; default mode writes inline scripts to navigate, screenshot, and report against goals.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
smoke-test
Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does…
test-fixing
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
multi-agent-e2e-validation
Multi-agent parallel E2E validation for database refactors. TRIGGERS - E2E validation, schema migration testing, database refactor validation.
symmetric-dogfooding
Bidirectional integration validation where two repositories validate each other before release.