rosetta extraction.instructions.md

A routing file that points extraction and data-work changes to smaller instruction files covering topics such as database safety, naming, compatibility, and authentication.

In plain words
What is it for?
Use it as a map when deciding which narrow extraction instruction files to read.
Why use it?
It keeps rules focused and helps an agent find the instructions relevant to a particular extraction change.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/tikoci/rosetta/extraction
Clone the repo
git clone --depth 1 https://github.com/tikoci/rosetta

Made for: GitHub Copilot.

Per session 166 This file is loaded in full into every session.
When invoked 166 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00166 $0.00166
Opus 5 $0.00083 $0.00083
Sonnet 5 $0.00033 $0.00033
Haiku 4.5 $0.00017 $0.00017

Measured 2d ago against content hash 760d6c4cc938, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rosetta extraction.instructions.md 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 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.

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.

.github/instructions/extraction.instructions.md · 18 lines

What it actually says

Extraction instruction map

The extraction surface now uses narrow rule files. Read the ones that match your change:

  • extractor-idempotent.instructions.md
  • extractor-import-side-effects.instructions.md
  • command-versions-vs-presence.instructions.md
  • schema-roundtrip-compat.instructions.md
  • data-source-naming-product-matrix.instructions.md
  • skill-attribution-boundary.instructions.md
  • github-api-auth.instructions.md

Keep this file as a router only. Put new extraction rules in the narrow file that actually owns them.

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.

  1. 2d ago First seen · 18 lines · 166 tokens per session scan A 760d6c4cc938

Subscribe to this mod's changes

rosetta extraction.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 16d ago), licensed MIT. It adds 166 tokens to every session, about $0.0008 per session on Opus 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-08-30.

Related

Other instructions, from other repositories