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 The-AI-Directory-Company/agents-and-skills --skill bug-report-writinggit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/bug-report-writing)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/bug-report-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/bug-report-writing/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/the-ai-directory-company/agents-and-skills/bug-report-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/bug-report-writing.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.00030 | $0.01333 |
| Opus 5 | $0.00015 | $0.00666 |
| Sonnet 5 | $0.00006 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
bug-report-writing 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Report Writing
Before you start
Gather the following from the user. If anything is missing, ask before proceeding:
- What broke? — The specific behavior that is wrong (not "it doesn't work")
- Where? — URL, screen, API endpoint, CLI command, or code path
- When did it start? — First observed date, or the deploy/commit that introduced it
- Who is affected? — All users, specific roles, certain browsers, percentage of requests
- How severe? — Is there a workaround? Is data at risk? Is revenue impacted?
If the user says something vague like "search is broken," push back: "What did you search for, what did you expect to see, and what appeared instead?"
Bug report template
Title
Use the format: [Component] Verb describing the failure — [trigger condition]
Good: "[Checkout] Payment form submits twice when user double-clicks Pay button" Bad: "Payment bug" or "Checkout issue" or "Double charge problem"
Summary
2-3 sentences covering WHAT is broken, WHO it affects, and WHEN it started. Include impact metrics if available.
Reproduction Steps
Write numbered steps that a developer with no context can follow to trigger the bug every time. Each step must describe exactly one action.
Precision rules:
- State exact inputs, not "enter some data"
- Include the starting state ("logged in as admin," "empty database," "feature flag X enabled")
- Note timing if relevant ("within 500ms," "after waiting 30 seconds")
- Specify the reproduction rate: always, intermittent (X/10 attempts), or one-time
Expected vs Actual Behavior
State both explicitly. Never assume the reader knows what "correct" means.
Expected: Clicking Pay multiple times submits only one payment.
Actual: Each click submits an independent payment request. User is charged per click.
Environment
Include every detail needed to reproduce: app version/commit, browser, OS, device, account type, feature flags, and API environment. The missing detail is always the one that matters.
What ships with it
1 file 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.
- 9d ago First seen · 114 lines · 30 tokens per session scan A 7b7c367573b6
bug-report-writing is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 1,333 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-09-03.
Other skills, from other repositories
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
deobfuscating-powershell-obfuscated-malware
Systematically deobfuscate multi-layer PowerShell malware using AST analysis, dynamic tracing, and tools like PSDecode and PowerDecode to reveal hidden payloads and C2 infrastructure.
detecting-process-injection-techniques
Detects and analyzes process injection techniques used by malware including classic DLL injection, process hollowing, APC injection, thread hijacking, and reflective loading. Uses memory forensics, API monitoring, and behavioral analysis to identify injection artifacts. Activates for requests involving process…
hunting-for-anomalous-powershell-execution
Hunt for malicious PowerShell activity by analyzing Script Block Logging (Event 4104), Module Logging (Event 4103), and process creation events. The analyst parses Windows Event Log EVTX files to detect obfuscated commands, AMSI bypass attempts, encoded payloads, credential dumping keywords, and suspicious download…
mobile-performance-react-native
React Native performance profiling, optimization, and monitoring - JS/UI thread analysis, re-render prevention, list optimization, image performance, bundle size, startup time, memory leaks, React Compiler, New Architecture benefits.
api-observability-axiom-pino-sentry
Pino logging, Sentry error tracking, Axiom - structured logging with correlation IDs, error boundaries, performance monitoring, alerting.