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 FortiumPartners/ensemble --skill smoke-test-critical-pathsgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/smoke-test-critical-paths)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/smoke-test-critical-paths"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/smoke-test-critical-paths/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/fortiumpartners/ensemble/smoke-test-critical-paths"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/smoke-test-critical-paths.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.00000 | $0.00417 |
| Opus 5 | $0.00000 | $0.00209 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
smoke-test-critical-paths 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 8d 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
Smoke Test Critical Paths Skill
Quick Reference - Load this first for fast context (~2KB)
Mission
Execute comprehensive critical user journey smoke tests to validate end-to-end business flows during release workflows.
Core Capabilities
- User Registration: Complete registration flow validation
- Authentication Journey: Login → Browse → Action → Logout flow
- Checkout Flow: Browse → Add to Cart → Checkout → Payment → Confirmation
- Search Journey: Search → Filter → View Results → Detail View
- Profile Management: Login → View Profile → Edit → Save → Verify
Quick Start
const { SmokeTestCriticalPaths } = require('./scripts/execute-journeys.js');
const tester = new SmokeTestCriticalPaths({
baseUrl: 'https://staging.example.com',
journeys: [
'registration',
'checkout',
'search'
]
});
const result = await tester.executeTests({
environment: 'staging'
});
if (result.passed) {
console.log('✅ Critical path tests passed');
}
Performance SLAs
const SLA_TARGETS = {
registration: 5000, // Registration flow: ≤5s
checkout: 8000, // Checkout flow: ≤8s
search: 3000, // Search flow: ≤3s
profile: 4000 // Profile management: ≤4s
};
Pass/Fail Criteria
Pass: All critical paths must complete successfully
- ✅ All journey steps execute without errors
- ✅ All SLA targets met
- ✅ Data persisted correctly
- ✅ User feedback/confirmations displayed
Fail: Any critical path failure blocks deployment
- ❌ Journey step fails or times out
- ❌ Data not persisted
- ❌ Missing confirmations or error states
Need More Detail?
Load: skills/smoke-test-critical-paths/REFERENCE.md (~10KB)
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.
- 8d ago First seen · 67 lines · 0 tokens per session scan A c716f5997271
smoke-test-critical-paths is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 417 tokens. 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-09-03.
Other skills, from other repositories
bmad-qa-generate-e2e-tests
Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]".
responsive-audit
Responsive audit: test pages at 375/768/1024px breakpoints via Playwright. Checks overflow, tap targets, sidebar collapse, text reflow, WCAG 1.4.4 zoom.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.