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 goiltpatpat/patpat --skill patpat-perfgit clone --depth 1 https://github.com/goiltpatpat/patpatWrote 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/goiltpatpat/patpat/patpat-perf)<a href="https://agentmods.dev/skills/goiltpatpat/patpat/patpat-perf"><img src="https://agentmods.dev/badge/skills/goiltpatpat/patpat/patpat-perf/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/goiltpatpat/patpat/patpat-perf"><img src="https://agentmods.dev/badge/skills/goiltpatpat/patpat/patpat-perf.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.00045 | $0.00344 |
| Opus 5 | $0.00023 | $0.00172 |
| Sonnet 5 | $0.00009 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
patpat-perf 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 10d 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
Patpat Performance
When invoked directly, read the operating protocol and execution graph in full. Do not load the router.
Read proof over proxy, fix root causes, and smallest safe change. Apply the performance playbook.
Measure the reported surface before reading toward a preferred cause. Keep workload, environment, warm-up, sample policy, and units comparable. Locate the dominant cost, change one causal variable, and preserve correctness and safety invariants.
When the objective requires sustained improvement toward a numeric target rather than one regression fix, apply the metric hillclimb playbook through patpat-run.
Report the baseline, post-change result, measurement noise, artifact locations, and remaining tradeoffs. Do not claim improvement from a single incomparable or proxy measurement.
Proof closure
Close repository mutations through:
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.
- 10d ago First seen · 24 lines · 45 tokens per session scan A b95462303337
patpat-perf is a skill published in the GitHub repository goiltpatpat/patpat (1 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 344 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-08-31.
Other skills, from other repositories
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
anchor-repro
Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe. Use for bug reports, failing tests, crashes, hangs, regressions, wrong output, and observable behavior that should change.
reqforge-greenkeeper
name: reqforge-greenkeeper description: Used when maintaining the ReqForge repository itself and its release gates fail — pnpm test, pnpm forge-smoke, pnpm sync:discover, adapter drift, skill fixtures, loadouts, or test-demo golden path. Restores a green, synced state with minimal changes. Not for bugs in user apps…
repair-prevention-assessment
A completion gate for fixes and self-repair work. It creates a machine-checkable assessment that separates evidence a current issue is closed from evidence that the fix will remain effective.
app-runtime-verify
Verify a built mobile or app runtime at runtime: run the app (device, emulator, or headless), read the captured runtime output (native logcat, iOS device log, or the Metro/JS console), classify any runtime errors against a per-stack taxonomy, and decide a PASS/FAIL runtime gate for the slice's acceptance behavior. The…