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/kint4/autoframe/bug-from-failurenpx skills add kint4/autoframe --skill bug-from-failuregit clone --depth 1 https://github.com/kint4/autoframeWrote 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/kint4/autoframe/bug-from-failure)<a href="https://agentmods.dev/skills/kint4/autoframe/bug-from-failure"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/bug-from-failure.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 | $0.00046 | $0.00429 |
| Opus 5 | $0.00023 | $0.00215 |
| Sonnet 5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
bug-from-failure 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 4d 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
/bug-from-failure — Failure to Bug Report
Type: Functional Description: Turns a test failure into a structured, shareable bug report with repro steps, severity, environment, and expected vs actual behavior.
Input Format
Any of:
- A failing test name or spec path
- A pasted failure log / stack trace / screenshot description
- A description of what went wrong
Output Format
A structured bug report in markdown:
### Title
[concise summary]
**Severity:** Critical / High / Medium / Low
**Environment:** [browser, base URL, env]
**Feature / Area:** [feature]
**Steps to Reproduce**
1. ...
**Expected Result**
...
**Actual Result**
...
**Evidence**
[log excerpt / screenshot / trace reference]
**Notes**
[suspected cause, related tests]
Step-by-Step Instructions
- Read the failing spec and its Page Object(s) to understand the intended behavior.
- Extract the failure signal (assertion that failed, error, step that broke).
- Before writing, confirm it's a real bug — if it looks like flake, route to
/flake-check. - Derive concrete, numbered repro steps from the test's actions.
- State expected vs actual clearly and factually.
- Assign severity based on user impact (blocking flow = Critical/High; cosmetic/edge = Medium/Low).
- Capture environment from
playwright.config.ts/.envvariables (never paste secret values). - Output the report in the format above, ready to paste into Jira / Linear / GitHub Issues.
Rules
- Report behavior, not implementation.
- Never include secret values from
.env. - If the cause is flake, defer to
/flake-checkinstead of filing a bug.
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.
- 4d ago First seen · 64 lines · 46 tokens per session scan A 0dda8dba983a
bug-from-failure is a skill published in the GitHub repository kint4/autoframe (6 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 429 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
k6-load-testing
Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
tokenless
Use when a task can be delegated through the globally installed Tokenless CLI without directly writing to the workspace; route it to a visible AI provider website to save agent tokens.
tokenless-install
Install, upgrade, repair, and verify Tokenless, its agent skills, and local Playwright runtime. Use only when the user explicitly asks for installation, upgrade, repair, browser sign-in handoff, a failed doctor check, or an installation integrity check.
agent-qa-authoring
Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.
agent-qa-debug-fix
Use after an agent-qa run has failed and you need to debug, patch, and verify the issue using MCP evidence, logs, artifacts, and local code changes instead of generated fix suggestions.