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/360-review-handoff.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/360-review-handoff)<a href="https://agentmods.dev/instructions/nczz/kiro-discord-bot/360-review-handoff"><img src="https://agentmods.dev/badge/instructions/nczz/kiro-discord-bot/360-review-handoff/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/360-review-handoff"><img src="https://agentmods.dev/badge/instructions/nczz/kiro-discord-bot/360-review-handoff.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.03990 | $0.03990 |
| Opus 5.5 | $0.01596 | $0.01596 |
| Sonnet 5.5 | $0.00798 | $0.00798 |
| Haiku 4.5 | $0.00399 | $0.00399 |
Grade A, and why
360-review-handoff 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
360 Review Handoff
This project expects evidence-first engineering. Do not answer from memory when the repo, runtime, logs, or official documentation can be checked. A good handoff explains the current system, the intended behavior, the actual behavior, the fix, the verification, and the remaining risk.
When a rule feels abstract, read review-examples.md before acting. It shows concrete bad and good patterns for review quality, helper reuse, runtime verification, and commit readiness.
When a task touches architecture direction, a recurring bug, or an intentionally unsupported behavior, read decision-failure-patterns.md. Do not leave major decisions or failure patterns only in chat history.
Operating Mindset
- At the start of each user request, briefly state what you will inspect or do next. Keep it factual and scoped; do not overpromise the outcome before evidence is gathered.
- Start from the real current state:
git status, diffs, tests, docs, runtime metadata, and logs. - Separate facts from inference. If a claim depends on source code, cite the file/function. If it depends on runtime, cite the command/log signal.
- Do not guess from memory. Prior memory can suggest where to look, but current code, current runtime state, current logs, or official docs must be checked before making a current-state claim.
- If evidence is unavailable, say what is unverified and why. Do not turn an assumption into a conclusion just to make the handoff look complete.
- Preserve user work. Never revert unrelated dirty files. If dirty files are in scope, inspect them and work with them.
- Prefer the repo's established paths, helpers, and policy layers over new local shortcuts.
- Treat Discord output, MCP tools, cron, cwd, and agent process control as security-sensitive surfaces.
- Keep docs, tests, and behavior aligned in the same change when the behavior is user-visible.
- While working, provide concise progress updates when moving between investigation, implementation, verification, and deployment. Each update should say what was learned or what is being checked next.
- Before finalizing, give an explicit go/no-go quality judgment and list what was actually verified.
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 Changed · +12 tokens per session dcd6112b1bea
- 1mo ago First seen · 276 lines · 3,978 tokens per session scan A 5669d618e354
360-review-handoff is an instructions file published in the GitHub repository nczz/kiro-discord-bot (44 stars, last pushed 16d ago), licensed MIT. It adds 3,990 tokens to every session, about $0.0160 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.