Borrowing it
Nothing to install: this file belongs to nczz/kiro-discord-bot. 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/nczz/kiro-discord-bot/main/.kiro/steering/review-examples.mdgit clone --depth 1 https://github.com/nczz/kiro-discord-botWrote 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/nczz/kiro-discord-bot/review-examples)<a href="https://agentmods.dev/instructions/nczz/kiro-discord-bot/review-examples"><img src="https://agentmods.dev/badge/instructions/nczz/kiro-discord-bot/review-examples/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/nczz/kiro-discord-bot/review-examples"><img src="https://agentmods.dev/badge/instructions/nczz/kiro-discord-bot/review-examples.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.02141 | $0.02141 |
| Opus 5.5 | $0.00856 | $0.00856 |
| Sonnet 5.5 | $0.00428 | $0.00428 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
review-examples 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Examples
Use this file with 360-review-handoff.md and decision-failure-patterns.md. The goal is not to memorize fixed answers. The goal is to recognize the difference between a surface pass and a review that can be trusted by the next engineer, operator, or agent.
60 vs 90+ Review
| Topic | 60-point answer | 90+ answer |
|---|---|---|
| Current state | "Looks fine" after reading the diff | Starts with git status, changed files, recent commits, runtime path, and exact untracked files |
| Intent | Repeats what changed | Explains the user problem, why this approach matches the architecture, and what behavior must not regress |
| Reuse | Accepts working code | Checks whether shared helpers already own the concern and flags duplicate security, formatting, path, cron, MCP, or audit logic |
| Risk | Mentions obvious bugs | Names failure modes: policy bypass, wrong Discord target, cwd pollution, secret leak, stuck worker, release artifact mismatch |
| Verification | Says tests pass | Lists exact commands or runtime signals, what each proves, and what remains unverified |
| Docs | Updates one README line | Checks README, .env.example, steering, release docs, i18n, command names, and log reason strings when behavior changes |
| Decisions | Leaves tradeoffs in chat | Records rejected shortcuts, non-goals, future triggers, and regression expectations when the direction matters |
| Handoff | Gives a summary | Gives findings first, evidence, go/no-go, residual risk, and next action |
Example: Discord Safe Egress
Bad implementation:
- Adds a local
splitEvery2000Charsnearbot_send_message. - Sends chunks with raw
ChannelMessageSendcalls. - Fixes only the reported long message but skips the owning egress semantics,
AllowedMentions, delivery audit, code fence repair, and MCP policy. - Tests the helper directly without proving the real tool path uses it.
High-quality implementation:
- Reuses
internal/discordfmt.Split,internal/discordfmt.WithPartPrefix, or an existing helper already built on them. - Keeps the established safe egress path/redaction for
bot_*tools, direct payload preservation fordiscord_*tools, mention suppression, policy checks, and audit events. - Tests long text, UTF-8, code fences, denied policy, Discord delivery errors, and the runtime tool path.
- Updates
discord-mcp.mdorproject.mdif the rule or supported behavior changed.
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 · 207 lines · 2,141 tokens per session scan A 432531067b8c
review-examples is an instructions file published in the GitHub repository nczz/kiro-discord-bot (44 stars, last pushed 16d ago), licensed MIT. It adds 2,141 tokens to every session, about $0.0086 per session on Opus 5.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-07.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.