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.
npx agentmods add instructions/tikoci/rosetta/db-meta-stampinggit clone --depth 1 https://github.com/tikoci/rosettaWrote 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/tikoci/rosetta/db-meta-stamping)<a href="https://agentmods.dev/instructions/tikoci/rosetta/db-meta-stamping"><img src="https://agentmods.dev/badge/instructions/tikoci/rosetta/db-meta-stamping.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 | $0.00151 | $0.00151 |
| Opus 5 | $0.00076 | $0.00076 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
rosetta db-meta-stamping.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 5d 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.
What it actually says
db_meta stamping
Released DBs must carry provenance keys such as release_tag, built_at, source_commit, and schema_version.
- Stamping happens in CI via
scripts/stamp-db-meta.ts. - Runtime entrypoints and docs should describe
db_metaas release provenance, not optional trivia. - If the key set or consumer behavior changes, update the workflow, the runtime readers, and the docs together.
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.
- 5d ago First seen · 12 lines · 151 tokens per session scan A 7b3ea4086f50
rosetta db-meta-stamping.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 19d ago), licensed MIT. It adds 151 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.
Other instructions, from other repositories
bun-pg-mcp AGENTS.md
AGENTS.md instructions for igoraguiar/bun-pg-mcp, covering agents.md, project context, tech stack, directory map and commands.
bun-mcp copilot-instructions.md
Copilot instructions for TomasHubelbauer/bun-mcp, covering github copilot instructions for the bun-mcp repository and formatting.
dbhub CLAUDE.md
Claude Code instructions for bytebase/dbhub, covering claude.md, dbhub development guidelines, commands, architecture overview and configuration.
plugin-files-mode
Rosetta Plugin Mode Bootstrap.
counterpoise-ledger CLAUDE.md
Instructions for jeffjjohnston/counterpoise-ledger, covering claude.md, project overview, development commands, essential commands and testing.
relay AGENTS.md
Instructions for ImBIOS/relay, covering agents.md — relay, project overview, tech stack, architecture and support policy.