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 summarybotng/summarybot-ng --skill bug-reporting-excellencegit clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/summarybotng/summarybot-ng/bug-reporting-excellence)<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/bug-reporting-excellence"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/bug-reporting-excellence/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/summarybotng/summarybot-ng/bug-reporting-excellence"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/bug-reporting-excellence.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.00033 | $0.01513 |
| Opus 5.5 | $0.00013 | $0.00605 |
| Sonnet 5.5 | $0.00007 | $0.00303 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
bug-reporting-excellence 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 1mo 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
86% identical to bug-reporting-excellence — 15 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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Reporting Excellence
<default_to_action> When reporting bugs:
- TITLE:
[Component] fails [Condition] causing [Impact] - DESCRIBE: Expected behavior → Actual behavior → Steps to reproduce
- INCLUDE: Environment, severity, screenshots/logs, business impact
- ISOLATE: Narrow down conditions (browser, user, amount thresholds)
- ONE BUG = ONE REPORT (don't combine issues)
Bug Report Formula:
## [Component] Issue Title
**Severity:** Critical/High/Medium/Low
**Environment:** Production/Staging/Dev
### Expected Behavior
What should happen
### Actual Behavior
What actually happens (with error messages)
### Steps to Reproduce
1. Step one
2. Step two
3. Observe issue
### Impact
How this affects users/business
Critical Success Factors:
- Reproducible steps (100%)
- Environment info (100%)
- Business impact stated (90%)
- Screenshots or logs (80%) </default_to_action>
Quick Reference Card
Severity Levels
| Level | Definition | Examples |
|---|---|---|
| Critical | System down, data loss, security | DB deleted, payments broken, credentials exposed |
| High | Major feature broken, many users | Can't checkout, search broken, dashboard fails |
| Medium | Partial break, workaround exists | Filter broken (refresh works), slow export |
| Low | Cosmetic, rare edge case | Button wraps on mobile, tooltip wrong color |
Title Formula
❌ Bad: "Checkout broken" ✅ Good: "Payment fails with Visa cards when order total > $1000"
Pattern: [Component] fails [Condition] causing [Impact]
Essential Information
Environment Details
Browser: Chrome 120.0.6099.109 (Windows)
OS: Windows 11 Pro
URL: https://example.com/checkout
Date/Time: 2025-10-17 14:23 UTC
User: [email protected] (ID: 12345)
Request ID: abc-123-def-456
Supporting Evidence
Error Messages:
{
"error": "Payment service unavailable",
"code": "GATEWAY_TIMEOUT",
"requestId": "abc-123-def-456"
}
Console Logs:
[ERROR] PaymentGateway: Connection timeout after 30000ms
at PaymentGateway.charge (gateway.js:145)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 231 lines · 33 tokens per session scan A 5fe362563f4d
bug-reporting-excellence is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 1,513 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to bug-reporting-excellence, differing in 15 lines, and is treated as a copy.
Other skills, from other repositories
bug-reporting-excellence
Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.
development-estimation
Use when estimating time, effort, cost, or complexity for features, projects, refactors, and bug backlogs. Produces defensible estimates via triage, decomposition, risk handling, and confidence intervals, with clear assumptions and validation steps.
triage-bug
Use when triaging a bug from session evidence (evidence-capture JSONL, replay JSONL, telemetry, repo-audit) instead of from a live user description, and producing a TDD fix plan plus a docs/bugs/{slug}.md triage artifact.
triage
Use this skill to systematically triage, categorize, prioritize, and label incoming issues, bug reports, and feature requests. Verifies reproducibility, identifies affected components, and assigns standardized workflow labels.
agent-qa-result-triage
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).