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-pr-submit.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-pr-submit)<a href="https://agentmods.dev/instructions/kurone-kito/idd-skill/idd-pr-submit"><img src="https://agentmods.dev/badge/instructions/kurone-kito/idd-skill/idd-pr-submit/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-pr-submit"><img src="https://agentmods.dev/badge/instructions/kurone-kito/idd-skill/idd-pr-submit.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.08933 | $0.08933 |
| Opus 5.5 | $0.03573 | $0.03573 |
| Sonnet 5.5 | $0.01787 | $0.01787 |
| Haiku 4.5 | $0.00893 | $0.00893 |
Grade C, and why
idd-skill idd-pr-submit.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 yesterday.
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-pr-submit.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 — 697 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDD — PR Submit Phase (D)
Read this file after the self-review loop passes. It covers pre-publication development-branch sync, claim verification, tests, pushing, PR creation, and waiting for CI.
Before the D1 sync and D2 push, apply the
shared claim revalidation gate.
{development-branch} below is the value resolved by
idd-work.instructions.md's
B1 Worktree creation Step 2
— re-resolve it here if this file is entered directly (for example,
on resume) without a fresh B1 pass.
D1 — Sync {development-branch} before first push
If the branch has not been pushed yet, sync it onto {development-branch}
before the first push — the routine pre-publication history cleanup step.
First run git fetch origin, then check whether the branch is
already current with origin/{development-branch}: if
git merge-base HEAD origin/{development-branch} equals
origin/{development-branch} (behind-count 0), the branch already
contains every commit on {development-branch}, so the rebase would be a
pure no-op. Skip the rebase entirely and proceed to D2 — D1's
pre-publication synchronization goal is already met. In a
sibling-worktree setup a no-op git rebase origin/{development-branch}
can still detach HEAD at the upstream tip without replaying the local
commit, and retrying that no-op re-detaches every time, so skip it.
Post-rebase verification cannot converge for that no-op.
Otherwise the branch is behind origin/{development-branch}: rebase
it onto {development-branch} (git rebase origin/{development-branch}),
then apply Post-rebase verification below.
After the first D-phase push, do not reuse D1 as the normal
synchronization path. Later branch updates should return through the
E-phase review loop and, by default, merge {development-branch} into
the published PR branch so the synchronization diff is reviewable.
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.
- yesterday Changed · +3 lines · +41 tokens per session 1f8bdc554fa1
- 2d ago Changed · +16 lines · +276 tokens per session 3e1b22f70048
- 7d ago Changed · -12 lines · -141 tokens per session 82b40dfc9d68
- 10d ago Changed d747fa14b106
- 12d ago Changed 8efee59bfe36
- 15d ago Changed · -7 tokens per session 100a17dd5597
- 20d ago Changed · +6 lines · +124 tokens per session fef1221a7969
- 23d ago Changed · -4 lines · -60 tokens per session 1aa8391ad654
- 24d ago Changed · +1 lines · +40 tokens per session 0962672ed09d
- 25d ago First seen · 687 lines · 8,660 tokens per session scan C 89828da11330
idd-skill idd-pr-submit.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,933 tokens to every session, about $0.0357 per session on Opus 5.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
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.