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 Espenandreass1/agentslice --skill fix-from-qa-reportgit clone --depth 1 https://github.com/Espenandreass1/agentsliceWrote 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/espenandreass1/agentslice/fix-from-qa-report)<a href="https://agentmods.dev/skills/espenandreass1/agentslice/fix-from-qa-report"><img src="https://agentmods.dev/badge/skills/espenandreass1/agentslice/fix-from-qa-report/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/espenandreass1/agentslice/fix-from-qa-report"><img src="https://agentmods.dev/badge/skills/espenandreass1/agentslice/fix-from-qa-report.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.00026 | $0.00193 |
| Opus 5 | $0.00013 | $0.00097 |
| Sonnet 5 | $0.00005 | $0.00039 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
fix-from-qa-report 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.
What it actually says
Fix From QA Report
Read
Verify the workspace and minimal preflight. Read the PR, changed files, coding rules, and the blocker evidence or exceptional QA report.
Guardrails
- Fix only approved blockers inside PR scope. A new area, lane, or user outcome needs reclassification and approval.
- Do not turn a
fast-buginto a broader feature silently; CI limits remain active. - Keep sensitive safeguards intact and require independent re-test.
Steps
- State only the blocker and intended fix.
- Implement the narrow fix and run focused checks.
- Update PR live status and request independent QA re-test.
Output
Report changed files, one-line checks, residual risk, and re-test next action. Do not create a duplicate status document.
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 Changed · -3 lines · -3 tokens per session ea5979cababc
- 9d ago First seen · 30 lines · 29 tokens per session scan A eb635dd995f0
fix-from-qa-report is a skill published in the GitHub repository Espenandreass1/agentslice (4 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 193 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.