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 live-system-verificationgit 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/live-system-verification)<a href="https://agentmods.dev/skills/paruff/ufawkesai/live-system-verification"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/live-system-verification/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/live-system-verification"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/live-system-verification.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.00065 | $0.01053 |
| Opus 5 | $0.00032 | $0.00526 |
| Sonnet 5 | $0.00013 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
live-system-verification 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 6d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live System Verification Skill
Why this exists
test.md mocks at every boundary by default — a reasonable rule for unit and
integration tests, but it means those tests can pass while the actual deployed
system does not work. This skill is the deliberate exception: no mocks, real
running dependency, real evidence.
⚠️ Environment target — CONFIRM before using
This skill is written substrate-agnostic on purpose because the actual target environment was not confirmed at time of writing:
- If uFawkesPipe: a
docker-compose.ymlwas observed alongside its.woodpecker.yml/Jenkinsfile— this may be a usable substrate for standing up real dependencies. Confirm before relying on it. - If uFawkesObs: no deploy-target evidence was available. Fill in Step 1 below with your actual mechanism (docker-compose, kind/k3d ephemeral cluster, existing staging namespace, or something else) before using this skill for real.
Do not run this skill until Step 1 is filled in for your actual stack.
Step 1 — Stand up the environment
<FILL IN: the exact command(s) to bring up a real, running instance of the component(s) under test for your stack. Examples of what this might look like, NOT prescriptions — verify against your own infra before using any of these:docker compose -f docker-compose.yml up -d, or applying GitOps overlays to an ephemeral kind/k3d cluster, or akubectl apply -k
overlays/ephemeral/. Do not guess at your own command from this list — confirm it works locally before wiring it into this skill.>
Wait for readiness (health check endpoint, docker compose ps showing
healthy, or equivalent) before proceeding. Record the readiness check and its
output as evidence.
Step 2 — Run the tagged tests
Run only the tests placed in the tests/live/ (or tests_live/) directory
per test.md's file placement convention, against the real endpoints/services
now running from Step 1. Examples of what these assertions typically look
like — verify current syntax for whichever tool you actually adopt, do not
assume these exact names are installed:
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.
- 6d ago First seen · 111 lines · 65 tokens per session scan A 2bb53c52101f
live-system-verification is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 17d ago), licensed MIT. It adds 65 tokens to every session and 1,053 once invoked, about $0.0003 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
flutter-skill
Automate and test Flutter applications — launch apps, inspect widgets, tap elements, enter text, scroll, swipe, take screenshots, validate state, and debug via Dart VM Service Protocol. Use when the user wants to run Flutter app tests, automate Flutter UI interactions, inspect widget trees, debug a running Flutter…
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
running-bug-review-board
Runs real-user QA, manual test plans, UX bug hunts, build sign-off, bug filing, and bug triage for web or iOS/iPadOS apps. Use when asked "QA this", "is this ready to ship?", or similar. Produces P0/P1/P2 bug reports, YES/NO phase sign-off, tracker sync guidance, and an HTML QA dashboard; keeps Interactive BRB triage…
mushi-integration
Full end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.