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 commands/chankov/agent-fleet/af-webperfgit clone --depth 1 https://github.com/chankov/agent-fleetWhat 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.00014 | $0.00459 |
| Opus 5 | $0.00007 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
af-webperf 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 3d 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.
This is a copy
92% identical to webperf — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/webperf targets web applications specifically. Do not use it for utility libraries, CLIs, or server-only code with no browser-facing output.
Determine the mode
Deep mode - activate when any of these is available:
- A Lighthouse JSON report file (e.g.
npx lighthouse <url> --output json --output-path ./report.json, ornpx -p chrome-devtools-mcp chrome-devtools lighthouse_audit --output-format=jsonfrom the Chrome DevTools MCP CLI) - A PageSpeed Insights JSON response (includes Lighthouse + CrUX)
- A CrUX API response (requires
CRUX_API_KEYorGOOGLE_API_KEY) - A DevTools performance trace
- A live URL plus the
chrome-devtoolsMCP server configured in the harness (the agent can capture metrics directly vialighthouse_auditandperformance_*tools) - The Chrome DevTools MCP CLI invoked locally (via
npx -p chrome-devtools-mcp chrome-devtools <tool>or afternpm i -g chrome-devtools-mcp) - the user runs commands likechrome-devtools lighthouse_audit --output-format=jsonand passes the JSON output to the agent
Quick mode - default when none of the above are available. The agent scans source code for structural anti-patterns and labels every finding as potential impact.
Run the audit
Delegate to the web-performance-auditor subagent (mention @web-performance-auditor). Pass it explicitly:
- The files, components, or diff under review
- Any artifact paths (Lighthouse JSON, PSI JSON, CrUX response, trace) or pasted JSON content
- The target URL or page name when known
- A note on which mode you expect (Quick or Deep), so the agent surfaces missing inputs if Deep was intended
The subagent returns a scorecard (only populated with sourced values), a ranked list of findings, positive observations, and proactive recommendations.
Output
Return the full audit report to the user. No synthesis or merge step is needed - this is a single-subagent command.
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.
- 3d ago First seen · 33 lines · 14 tokens per session scan A 41af6505759b
af-webperf is a command published in the GitHub repository chankov/agent-fleet (10 stars, last pushed 7d ago), licensed MIT. It adds 14 tokens to every session and 459 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to webperf, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.