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-merge.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-merge)<a href="https://agentmods.dev/instructions/kurone-kito/idd-skill/idd-merge"><img src="https://agentmods.dev/badge/instructions/kurone-kito/idd-skill/idd-merge.svg" alt="Measured on agentmods" 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.06714 | $0.06714 |
| Opus 5 | $0.03357 | $0.03357 |
| Sonnet 5 | $0.01343 | $0.01343 |
| Haiku 4.5 | $0.00671 | $0.00671 |
Grade C, and why
idd-skill idd-merge.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 2d 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-merge.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 — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDD — Merge Execution Phase (F3–F5)
Read only after idd-merge-handoff.instructions.md routes the current
claim to the autonomous merge path. Covers executing the merge (F3),
cleanup (F4), and looping back to discover (F5).
The final merge-gate timing defaults are named in IDD policy constants; the merge logic itself stays here.
Before any mutating action in F3, apply the shared claim revalidation gate.
F3 — Merge
- Confirm the claim is still yours: the active claim must still use
your current
{claim-id}. If it is missing, released, or held by a different{claim-id}(even under the same agent ID), the claim was lost — report and stop. - Defensive route check: re-read the repository's recorded merge
policy (missing → treat as
human_merge, the distributed default). Then apply:fully_autonomous_merge: continue.separate_merge_agent: continue only when repository documentation explicitly records the current session as the designated merge-capable actor and the documented resume condition is satisfied; otherwise route toidd-merge-handoff.instructions.mdand stop.human_mergeor unknown policy: route toidd-merge-handoff.instructions.mdand stop.
- Immediately before executing the merge command, do one final live
fetch using the exact same activity-universe scope as E1 Step 1
(all review threads, review bodies, and regular PR comments,
excluding trusted agent operational marker comments), and compare it
against the F2 snapshot carried forward from
idd-pre-merge.instructions.md. When helper runtime is enabled, prefer the documented merge-gate helper reference indocs/idd-helper-scripts.mdto collect the snapshot tuple and broaderpre-merge-readinessJSON report. Both helpers remain read-only evidence collectors only: if execution fails, output is invalid JSON, required sections are missing, or live GitHub state disagrees with it, discard helper output and run the live fetch directly — the written gate rules remain canonical. Return to E1 if any of F2's Review-currency return-to-E1 triggers apply, substituting the carried F2-snapshot fields for F2's own stored watermark fields:{f2-head-SHA}for{head-SHA},{f2-max-activity-updatedAt}for{max-activity-updatedAt},{f2-total-item-count}for{total-item-count}, and{f2-latest-ci-completed-at}for{latest-ci-completed-at}— this final fetch is the live side of each comparison, exactly as F2's own live snapshot was.
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.
- 2d ago Changed · +55 lines · +757 tokens per session 386eda4e9dc3
- 8d ago First seen · 456 lines · 5,957 tokens per session scan C cc4f8339a028
idd-skill idd-merge.instructions.md is an instructions file published in the GitHub repository kurone-kito/idd-skill (11 stars, last pushed today), licensed MIT. It adds 6,714 tokens to every session, about $0.0336 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
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).
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.
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).
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.