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-onboarding.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-onboarding)<a href="https://agentmods.dev/instructions/himanshusaini-afk/buggy/buggy-onboarding"><img src="https://agentmods.dev/badge/instructions/himanshusaini-afk/buggy/buggy-onboarding/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-onboarding"><img src="https://agentmods.dev/badge/instructions/himanshusaini-afk/buggy/buggy-onboarding.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.00372 | $0.00372 |
| Opus 5 | $0.00186 | $0.00186 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
buggy buggy-onboarding.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 — Onboarding Assistant
When a file is opened that has known bug history (tracked in .debugger/bug-report.md), proactively inform the developer about past issues and risk areas.
When to Activate
When providing context about a file, check if .debugger/bug-report.md exists. If it does, read it and include relevant history in your responses.
What to Share
When a developer is working in a file with bug history:
- High-risk functions — functions that have had proven bugs before
- Common patterns — recurring bug types in this file (e.g., "this file has had 3 off-by-one errors")
- Open bugs — any proven bugs that haven't been fixed yet
- Related fixes — patches that were applied to similar bugs in this file
Format
Keep it brief and contextual — don't dump the full report. Example:
💡 Context: This file (src/cart.ts) has had 4 proven bugs historically:
• calculateSubtotal — negative result for cheap items (fixed)
• calculateAveragePrice — NaN on empty array (fixed)
• applyDiscount — negative total with discount > 100% (fixed)
• calculateRelatedTotal — infinite recursion with cycles (open ⚠️)
Be careful with the relatedMap parameter in calculateRelatedTotal.
Rules
- Only mention this when it's relevant to what the user is doing
- Don't repeat the same warning in every response
- Prioritize OPEN (unfixed) bugs over historical fixed ones
- If the user is modifying a function with past bugs, warn once
- If no bug report exists or the file has no history, say nothing
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 · 43 lines · 372 tokens per session scan A bbd44f552966
buggy buggy-onboarding.md is an instructions file published in the GitHub repository himanshusaini-afk/buggy (0 stars, last pushed 3d ago), licensed MIT. It adds 372 tokens to every session, about $0.0019 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).