Borrowing it
Nothing to install: this file belongs to kurone-kito/idd-skill. 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/kurone-kito/idd-skill/main/.github/instructions/idd-review-triage.instructions.mdgit clone --depth 1 https://github.com/kurone-kito/idd-skillWrote 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/kurone-kito/idd-skill/idd-review-triage)<a href="https://agentmods.dev/instructions/kurone-kito/idd-skill/idd-review-triage"><img src="https://agentmods.dev/badge/instructions/kurone-kito/idd-skill/idd-review-triage/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/kurone-kito/idd-skill/idd-review-triage"><img src="https://agentmods.dev/badge/instructions/kurone-kito/idd-skill/idd-review-triage.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.08148 | $0.08148 |
| Opus 5 | $0.04074 | $0.04074 |
| Sonnet 5 | $0.01630 | $0.01630 |
| Haiku 4.5 | $0.00815 | $0.00815 |
Grade C, and why
idd-skill idd-review-triage.instructions.md scanned grade C with 1 finding 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 today.
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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- idd-generated-from: idd-template/.github/instructions/idd-review-triage.instructions.md Generated by sync-docs. Edit the source above, then run `node scripts/sync-docs.mjs --apply`; do not edit this file. --> How it starts
The opening of the file, as written. The whole thing — 619 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDD — Review Triage Phase (E4–E8)
Read this file after idd-review-snapshot.instructions.md (E3) finds
ReviewItems_snapshot non-empty. Covers classifying, scoring, recording
dispositions, and counting accepted items.
Before posting any E-phase operational comment or GitHub reply, apply
the shared claim revalidation gate. The active claim must still use your
current {claim-id}.
Skip condition E8: if the Accepted PATH A count after verification
is zero, proceed to the E-phase branch-sync check below (its
no-sync-required clean/behind-no-conflict exit applies the
Zero-Accepted-PATH-A advisory re-review gate).
E4 — Classify and score ReviewItems_snapshot
For each item in ReviewItems_snapshot, first classify it:
- PATH A — actionable feedback: human reviewer threads and regular
comments,
CHANGES_REQUESTEDreview bodies, and critique-pass findings that require a code change or maintainer decision. - PATH B — advisory feedback: Copilot and CI advisory bot comments included by E1 for traceability, even when they do not require a code change.
- If classification is ambiguous, default to PATH A.
- Record each PATH A actor's permission standing (CODEOWNER, required reviewer, Triage/Write/Maintain/Admin, or none) — E5's cap reads it.
Advisory non-review notice. Before scoring a PATH B item, decide whether it is a completed advisory review of the current HEAD or an advisory non-review notice — an advisory bot comment reporting that it did not review the current HEAD: rate-limit / quota / credit-exhaustion warnings, queued / in-progress status, a bare request acknowledgement (e.g. CodeRabbit "Actions performed"), or an error / "temporarily unavailable" notice. A non-review notice carries no advisory result to score; handle it with the E6 non-review-notice rule instead of the normal PATH B disposition.
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.
- today Changed · +13 lines · +200 tokens per session 09ab1762de70
- 4d ago Changed · +1 lines · +8 tokens per session e7765da6cc5f
- 5d ago Changed · +6 lines · +82 tokens per session 83f62ac0009d
- 10d ago First seen · 599 lines · 7,858 tokens per session scan C 04ea22e6f22f
idd-skill idd-review-triage.instructions.md is an instructions file published in the GitHub repository kurone-kito/idd-skill (11 stars, last pushed today), licensed MIT. It adds 8,148 tokens to every session, about $0.0407 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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).
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.
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).
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.