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 paruff/uFawkesAI --skill performance-smoke-testinggit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/performance-smoke-testing)<a href="https://agentmods.dev/skills/paruff/ufawkesai/performance-smoke-testing"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/performance-smoke-testing/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/paruff/ufawkesai/performance-smoke-testing"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/performance-smoke-testing.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.00030 | $0.00880 |
| Opus 5 | $0.00015 | $0.00440 |
| Sonnet 5 | $0.00006 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
performance-smoke-testing 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Performance Smoke Testing
Load trigger:
"load performance-smoke-testing skill"> DORA: Cap 5 (Small Batches / Shift Left on Quality) Token cost: Low
Purpose
Validate basic performance characteristics to detect regressions.
Responsibilities
- Run lightweight load tests
- Measure latency, throughput, error rate
- Detect performance regressions
- Produce performance summary
Inputs
- Build output
- Performance test configuration
- Baseline metrics (if available)
Outputs
performance-smoke.jsonperformance-summary.md
Metrics
Core Metrics
| Metric | Description | Unit |
|---|---|---|
| Latency (p50) | Median response time | ms |
| Latency (p95) | 95th percentile response time | ms |
| Latency (p99) | 99th percentile response time | ms |
| Throughput | Requests per second | req/s |
| Error rate | Percentage of failed requests | % |
| Saturation | Resource utilization at peak | % |
Regression Thresholds
| Metric | Regression If... |
|---|---|
| Latency (p50) | > 20% increase from baseline |
| Latency (p95) | > 30% increase from baseline |
| Throughput | > 15% decrease from baseline |
| Error rate | > 1% increase from baseline |
Test Configuration
Light Smoke Test
- Duration: 30 seconds
- Concurrent users: 10
- Requests per user: 50
- Think time: 100ms
Standard Smoke Test
- Duration: 60 seconds
- Concurrent users: 50
- Requests per user: 100
- Think time: 200ms
Validation Rules
Pre-Test
- Application accessible
- Baseline metrics available (or first run noted)
- Test parameters configured
During Test
- No errors exceeding threshold
- No timeouts exceeding threshold
- Resource utilization within bounds
Post-Test
- Results collected and formatted
- Regression assessment made
- Comparison with baseline (if available)
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.
- 5d ago First seen · 143 lines · 30 tokens per session scan A 81e042a8d6f7
performance-smoke-testing is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 16d ago), licensed MIT. It adds 30 tokens to every session and 880 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
template-formal
Strongly-typed multiagent ant-robot colony exemplar — ADTs, session-typed protocols, affine-discipline resource handles, storage-as-functor framing, Active-Inference-flavored decision loop, mypy-as-oracle negative controls.
template-reproducibility-audit
Deterministic reproducibility audit — fixed seeds, regenerate-from-clean, double-run diff before Zenodo/arXiv/release. USE WHEN outputs drift between runs, "worked on my machine", need regenerate-from-clean proof, or pre-release reproducibility check — even without naming docs/prompts.
template-test-creation
Create pytest suites under the no-mocks policy — real data, temp files, subprocess, pytest-httpserver. USE WHEN adding tests, raising coverage, testing new src/ module, or user forbids mocks.
infrastructure-benchmark
Deterministic benchmark harnesses for public template exemplars. Use when scoring generated project outputs against benchmark manifests, refreshing the default template smoke manifest, checking publication-readiness rubrics, or adding bounded no-network readiness checks for public template outputs.
infrastructure-sia
Skill for the Self-Improvement Agent (SIA) harness contract. Use when validating task public/private layouts, generation artifact trees, evaluation runners, fixture replay loops, or opt-in live Meta→Target→Feedback cycles in template projects.
template-sia
SIA (Self-Improvement Agent) harness exemplar — Meta/Target/Feedback loops, public/private splits, fixture replay, fail-closed validation.