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 agentmods add skills/greglas75/zuvo/performance-auditnpx skills add greglas75/zuvo --skill performance-auditgit clone --depth 1 https://github.com/greglas75/zuvoWhat 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 | $0.00090 | $0.07411 |
| Opus 5 | $0.00045 | $0.03705 |
| Sonnet 5 | $0.00018 | $0.01482 |
| Haiku 4.5 | $0.00009 | $0.00741 |
Grade A, and why
performance-audit 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
readFileSync, writeFileSync, execSync, crypto.pbkdf2Sync How it starts
The opening of the file, as written. The whole thing — 715 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:performance-audit
Measure, score, and prioritize performance across the entire stack. Every finding carries an Impact Model (estimated savings, blast radius, confidence level) so the team can act on data instead of hunches.
When to use: Periodic health check, before major release, after heavy feature
work, when users report slowness, before scaling infrastructure.
When NOT to use: Code quality (zuvo:review), security (/security-audit),
test quality (/test-audit).
Guiding Principles
- Performance claims without measurement are opinions, not findings.
- "Slow" without a baseline and a target is meaningless.
- Optimization without profiling is premature optimization.
- When evidence is absent, report INSUFFICIENT DATA -- never guess.
Mandatory File Loading
Read every file below before starting. Print the checklist.
CORE FILES LOADED:
1. ../../shared/includes/codesift-setup.md -- [READ | MISSING -> STOP]
2. ../../shared/includes/env-compat.md -- [READ | MISSING -> STOP]
3. ../../rules/cq-patterns.md -- [READ | MISSING -> STOP]
4. ../../shared/includes/run-logger.md -- [READ | MISSING -> STOP]
5. ../../shared/includes/retrospective.md -- [READ | MISSING -> STOP]
If any file is MISSING, STOP. Do not proceed from memory.
Conditional Files
| File | Load when |
|---|---|
../../rules/cq-checklist.md |
Scoring cross-cutting CQ overlap (CQ6 resources, CQ7 unbounded, CQ17 N+1) |
Argument Parsing
| Token | Behavior |
|---|---|
(empty) or full |
All applicable dimensions across the entire project |
[path] |
Scope to a directory or module |
[file] |
Deep single-file audit (algorithms, memory, complexity) |
--frontend |
D1-D3, D10 only |
--backend |
D4-D5, D7-D8, D11-D12 only |
--db |
D7 only (database queries and schema) |
--bundle |
D2 only (bundle weight analysis) |
Safety Gate
This audit is read-only. The only write target is zuvo/audits/. Do not modify
source files, configs, build output, or runtime environments. Tooling probes
(bundle analysis, Lighthouse) may be invoked but must not alter the build.
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.
- 2d ago First seen · 715 lines · 90 tokens per session scan A 08bee70c27fb
performance-audit is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 90 tokens to every session and 7,411 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:opening-pull-requests
Open a GitHub Pull Request with automatic base branch detection, scope allowlist enforcement, PR template filling, and post-create base verification. Replaces ring:generating-pr-descriptions. Use after pushing a branch when ready to open a PR. Skip if the branch is not yet pushed or there are uncommitted changes …
ring:cleaning-comments
Cleaning redundant and obvious comments following clean code principles while preserving meaningful documentation. Supports git scope filtering (staged, unstaged, branch, commit-range). Use when code has excessive comments, during code review, or post-refactor cleanup. Skip when reviewing documentation files or…