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/sawyerhood/dev-browser-eval/update-success-rategit clone --depth 1 https://github.com/SawyerHood/dev-browser-evalWrote 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/commands/sawyerhood/dev-browser-eval/update-success-rate)<a href="https://agentmods.dev/commands/sawyerhood/dev-browser-eval/update-success-rate"><img src="https://agentmods.dev/badge/commands/sawyerhood/dev-browser-eval/update-success-rate.svg" alt="Measured on agentmods" 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.00014 | $0.00281 |
| Opus 5 | $0.00007 | $0.00140 |
| Sonnet 5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
update-success-rate 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.
What it actually says
Update Benchmark Success Rates
Check the last line of all JSONL files in benchmark-results/ to verify task completion and update the success rate column in benchmark-comparison.md.
Steps
- Find all
*.jsonlfiles inbenchmark-results/ - Read the last line of each file (contains the final result JSON)
- For each run, check if:
- The task completed successfully (
"subtype":"success") - The average score is correct (should be 9.0)
- The task completed successfully (
- Calculate success rate for each method (dev-browser, playwright-mcp, playwright-skill)
- Update the table in
benchmark-comparison.mdwith the Success Rate column
Success Criteria
A run is successful if:
- The result shows
"subtype":"success" - The result mentions an average score of 9.0 (not 8.0 or other values)
Output Format
Update the markdown table to include:
| Method | Time | Cost (USD) | Turns | Success Rate |
Where Success Rate shows the percentage and fraction, e.g., 100% (3/3) or 67% (2/3).
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 · 34 lines · 14 tokens per session scan A 7dbb8a8cee99
update-success-rate is a command published in the GitHub repository SawyerHood/dev-browser-eval (23 stars, last pushed 8mo ago), licensed MIT. It adds 14 tokens to every session and 281 once invoked, about $0.0001 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-30.
Other commands, from other repositories
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.