A command that turns a description of a software problem into a structured bug report. It records what happened, what should have happened, how to reproduce it, where it occurred, and what evidence is available.

Use it to document defects with reproduction steps, severity, priority, environment details, expected and actual results, logs, and screenshots.

It gives developers the details needed to reproduce and fix an issue without repeatedly asking for missing context.

bug-report — Command for coding agents by latestaiagents: A command that turns a description of a software…

Install

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.

agentmods

npx agentmods add commands/latestaiagents/agent-skills/bug-report

Clone the repo

git clone --depth 1 https://github.com/latestaiagents/agent-skills

Or install qa-testing, the plugin that ships this one along with the rest of its 6 skills, 3 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/latestaiagents/agent-skills/bug-report.svg)](https://agentmods.dev/commands/latestaiagents/agent-skills/bug-report)

Your own site

<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/bug-report"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/bug-report.svg" alt="Measured on agentmods" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 347 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00010	$0.00347
Opus 5	$0.00005	$0.00173
Sonnet 5	$0.00002	$0.00069
Haiku 4.5	$0.00001	$0.00035

Measured today against content hash d777e0e938e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bug-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 today.

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.

plugins/qa-testing/commands/bug-report.md · 78 lines

What it actually says

/bug-report

Create a well-structured bug report that developers can act on.

What I Need

Tell me:

What went wrong?
What did you expect?
Steps you took before the bug
Environment (browser, OS, app version)
Any error messages or screenshots?

What I'll Create

A complete bug report with:

Clear title - Descriptive summary
Severity/Priority - Impact assessment
Environment - Where it happened
Steps - Exact reproduction path
Expected vs Actual - Clear comparison
Evidence - Screenshots, logs guidance

Bug Report Format

## Bug: [Title]

### Severity: [Critical/High/Medium/Low]
### Priority: [P0/P1/P2/P3]

### Environment
- OS:
- Browser:
- App Version:

### Steps to Reproduce
1. ...
2. ...
3. ...

### Expected Result
[What should happen]

### Actual Result
[What happens]

### Evidence
[Screenshots, logs, videos]

Example

You: /bug-report

The save button doesn't work after editing profile.
Chrome on Mac. No error shown.

Claude: [Structures complete bug report with clear steps,
suggests what evidence to collect, asks clarifying
questions about frequency and workarounds]

Quality Checks

I'll ensure your report:

Has reproducible steps
Includes environment details
Documents expected behavior
Suggests evidence to attach
Uses appropriate severity

Changes

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.

today First seen · 78 lines · 10 tokens per session scan A d777e0e938e5

Subscribe to this mod's changes

bug-report is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 347 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-09-03.

Debugging agentic-ai agentic-rag agentic-workflow agentshub agentskills ai

bug-report

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/bug-report

What I Need

What I'll Create

Bug Report Format

Example

Quality Checks

What this file has done since we first saw it

Other commands, from other repositories

fdk-react-create

fdk-refactor

fw-setup-uninstall

fw-setup-troubleshoot

git

checklist