What is idd-skill idd-review-snapshot.instructions.md?

A set of instructions for collecting and reviewing comments and other review items on a GitHub pull request.

It is for fetching review data, running a critique pass, and deciding whether the review list is empty or needs further triage.

It helps the agent use one recorded pull-request commit while gathering all review threads, including resolved ones, so feedback is not missed.

How kurone-kito/idd-skill configures GitHub Copilot

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/kurone-kito/idd-skill/main/.github/instructions/idd-review-snapshot.instructions.md

Clone the repo

git clone --depth 1 https://github.com/kurone-kito/idd-skill

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/kurone-kito/idd-skill/idd-review-snapshot/github.svg)](https://agentmods.dev/instructions/kurone-kito/idd-skill/idd-review-snapshot)

Your own site

<a href="https://agentmods.dev/instructions/kurone-kito/idd-skill/idd-review-snapshot"><img src="https://agentmods.dev/badge/instructions/kurone-kito/idd-skill/idd-review-snapshot/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/kurone-kito/idd-skill/idd-review-snapshot"><img src="https://agentmods.dev/badge/instructions/kurone-kito/idd-skill/idd-review-snapshot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,379 This file is loaded in full into every session.

When invoked 3,379 The same file — it is already loaded in full.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.03379	$0.03379
Opus 5	$0.01690	$0.01690
Sonnet 5	$0.00676	$0.00676
Haiku 4.5	$0.00338	$0.00338

Measured 4d ago against content hash 0cf0af5ab3fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade C, and why

idd-skill idd-review-snapshot.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 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.

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-snapshot.instructions.md Generated by sync-docs. Edit the source above, then run `node scripts/sync-docs.mjs --apply`; do not edit this file. -->

.github/instructions/idd-review-snapshot.instructions.md · 273 lines

How it starts

The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.

IDD — Review Snapshot Phase (E1–E3)

Read this file after CI passes on a newly pushed PR, or after returning from a fix cycle. It covers fetching review items (E1), running the critique pass (E2), and checking whether ReviewItems_snapshot is empty (E3).

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} — this also serves as E1's phase-entry self-check: E1 re-fetches all of its state from GitHub on every entry, so, unlike B1/B3, there is no local plan or worktree artifact that could go stale between checks.

If ReviewItems_snapshot is empty after E3: proceed to the E-phase branch-sync check in idd-review-triage.instructions.md. If ReviewItems_snapshot is non-empty after E3: proceed to idd-review-triage.instructions.md (E4).

E1 — Fetch review items into ReviewItems_snapshot

Step 1 — Snapshot the activity universe. First, read the current PR HEAD SHA from the GitHub API and store it as {head-SHA}. Do not re-read the HEAD SHA during Steps 1–3; use this single stored value throughout. Then fetch all of the following from GitHub in a single pass (before applying any exclusion filters):

All review threads (resolved or not) — paginate until hasNextPage is false; do not stop at a fixed page size such as first: 20, as that would miss threads when the total count exceeds the page size
All review body submissions (any reviewer state)
All regular PR comments

Exclude trusted agent operational comments from the snapshot: comments whose body begins with one of these exact operational marker prefixes and whose GitHub author is a trusted marker actor per idd-overview-core.instructions.md:

<!-- review-watermark:
<!-- review-baseline:
<!-- claimed-by:
<!-- unclaimed-by:
advisory-wait:
advisory-wait-recovery:
<!-- advisory-wait:
advisory-reroll:

Read the full file on GitHub · 273 lines

Changes

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 Changed · +14 lines · +214 tokens per session 0cf0af5ab3fd
9d ago First seen · 259 lines · 3,165 tokens per session scan C bf68bc2813fc

Subscribe to this mod's changes

idd-skill idd-review-snapshot.instructions.md is an instructions file published in the GitHub repository kurone-kito/idd-skill (11 stars, last pushed yesterday), licensed MIT. It adds 3,379 tokens to every session, about $0.0169 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.

Code review Git and workflow claude-skills codex-skills copilot-skills development-automation idd skills-prompts

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

idd-skill: Instructions file for GitHub Copilot