Borrowing it
Nothing to install: this file belongs to himanshusaini-afk/buggy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/himanshusaini-afk/buggy/main/.kiro/steering/buggy-bug-trends.mdgit clone --depth 1 https://github.com/himanshusaini-afk/buggyWrote 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/instructions/himanshusaini-afk/buggy/buggy-bug-trends)<a href="https://agentmods.dev/instructions/himanshusaini-afk/buggy/buggy-bug-trends"><img src="https://agentmods.dev/badge/instructions/himanshusaini-afk/buggy/buggy-bug-trends/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/instructions/himanshusaini-afk/buggy/buggy-bug-trends"><img src="https://agentmods.dev/badge/instructions/himanshusaini-afk/buggy/buggy-bug-trends.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.00529 | $0.00529 |
| Opus 5 | $0.00264 | $0.00264 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
buggy buggy-bug-trends.md 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
Buggy — Bug Trend Tracking
After every Buggy investigation that finds a confirmed bug, update the bug trend report at .debugger/bug-report.md.
When to Update
After any buggy_investigate call returns status: "confirmed_and_repaired" or status: "confirmed_no_repair".
Report Format
Maintain .debugger/bug-report.md with this structure:
# Bug Trend Report
Last updated: [timestamp]
## Summary
| Metric | Count |
|--------|-------|
| Total investigations | X |
| Bugs proven | Y |
| Fixes applied | Z |
| Open (unfixed) | W |
## By File (Risk Heatmap)
| File | Bugs Found | Fixed | Open | Risk |
|------|-----------|-------|------|------|
| src/cart.ts | 4 | 3 | 1 | 🔴 High |
| src/payments.ts | 2 | 2 | 0 | 🟢 Clean |
| src/auth.ts | 1 | 0 | 1 | 🟡 Medium |
## Bug Patterns
| Pattern | Occurrences | Example |
|---------|-------------|---------|
| Unclamped numeric input | 3 | discount > 100% |
| Division by zero | 2 | empty array .length |
| Non-determinism | 1 | Math.random in logic |
## Recent Bugs
### [date] — calculateSubtotal (src/cart.ts)
- **Type:** Negative result from unclamped subtraction
- **Trigger:** `{price: 0.5, quantity: 15}`
- **Status:** Fixed ✓
- **Fix:** Guard `item.price > 2` before bulk discount
### [date] — calculateAveragePrice (src/cart.ts)
- **Type:** Division by zero
- **Trigger:** `[]` (empty array)
- **Status:** Fixed ✓
- **Fix:** Early return 0 for empty array
Rules
- Only add entries for PROVEN bugs (with certificates), not speculative issues
- Mark bugs as "Fixed ✓" when an approved patch is applied
- Update the risk heatmap colors based on open bug count:
- 0 open = 🟢 Clean
- 1 open = 🟡 Medium
- 2+ open = 🔴 High
- Keep the "Recent Bugs" section to last 20 entries
- Update "Bug Patterns" by grouping similar root causes
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 · 72 lines · 529 tokens per session scan A ca119c0d28ff
buggy buggy-bug-trends.md is an instructions file published in the GitHub repository himanshusaini-afk/buggy (0 stars, last pushed 3d ago), licensed MIT. It adds 529 tokens to every session, about $0.0026 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-08.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).