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/local-db-groundinggit 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/local-db-grounding)<a href="https://agentmods.dev/instructions/tikoci/rosetta/local-db-grounding"><img src="https://agentmods.dev/badge/instructions/tikoci/rosetta/local-db-grounding.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.01024 | $0.01024 |
| Opus 5 | $0.00512 | $0.00512 |
| Sonnet 5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
rosetta local-db-grounding.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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local DB grounding
Dev mode (resolveDbPath → project root) serves the repo-root ros-help.db — a
git-ignored file whose contents are arbitrary local state. It is not trusted by
default. Before grounding any claim about shipped data on it, verify it.
The rule
- The latest CI-built release DB is the source of truth for grounding claims.
It is what
bunx @tikoci/rosettaconsumers actually get.make db-sync(scripts/db-sync.ts) fetches it into the resolved path (atomic replace — safe while an MCP server holds the old file open).- It does not use
--refresh: that pins the URL topackage.json's version, which in a checkout is a CI-rewritten placeholder (v0.11.0-rc.0) with no release, and falls back to/releases/latest— the newest stable, which lags the prerelease schema.db-syncinstead usesghto find the newest release (prereleases included) that actually shipsros-help.db.gz, then reuses the hardeneddownloadDb()(schema/content validation + stale-sidecar cleanup + atomic swap) via itsurlsOverrideparam. Requires theghCLI. Keep it this way.
- It does not use
make extractproduces an unstamped local working DB — for extraction and pipeline work, not for claims about shipped data.db-doctorreports it asunstamped; that is expected, not a failure to "fix" by re-extracting.- Verify before trusting.
make db-doctor(orbun run db:doctor) prints the resolved path +db_metaprovenance + a grounding verdict and exits non-zero when notok. In-session, onerouteros_statscall returns the sameprovenance.groundingblock — prefer it over shelling into sqlite.
The verdict (classifyDbGrounding, src/paths.ts)
Pure function, shared by routeros_stats (getDbStats), MCP startup, and
db-doctor. Status precedence:
| status | meaning | typical fix |
|---|---|---|
schema_mismatch |
PRAGMA user_version ≠ code SCHEMA_VERSION |
make db-sync |
internal_inconsistent |
db_meta.schema_version ≠ pragma — a corpus bumped in place by initDb(); provenance no longer describes the bytes (the #94 "Frankenstein") |
make db-sync |
unstamped |
neither release_tag nor source_commit — a local make extract build |
fine for extraction; make db-sync to ground |
provenance_incomplete |
claims release identity but is missing one of the four CI stamps (release_tag/source_commit/built_at/schema_version), or a stamped version that won't parse — fail closed |
make db-sync |
tag_behind |
release_tag base version behind the checkout |
make db-sync |
ok |
all four stamps present, schema coherent, tag current | — |
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 First seen · 62 lines · 1,024 tokens per session scan A eb704903baca
rosetta local-db-grounding.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 18d ago), licensed MIT. It adds 1,024 tokens to every session, about $0.0051 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
apple-health-mcp AGENTS.md
Instructions for neiltron/apple-health-mcp, covering repository guidance, project, validate changes, code map and invariants.
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.
invoice-builder copilot-instructions.md
Copilot instructions for piratuks/invoice-builder, a project described as: Invoice and quotation builder desktop app with PDF export, designed for small businesses and freelancers. Create, manage, and export invoices and quotes easily using a local database in an Electron-based app.
mcp-server-excel documentation-structure.instructions.md
Instructions for sbroenne/mcp-server-excel, covering documentation structure & standards, 📁 documentation hierarchy, root level - essential user-facing only, docs/ - canonical documentation and specs/ - feature specifications.
mcp-server-powerpoint mcp-server-guide.instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering mcp server development guide, llm-facing content rules, two kinds of tools: hand-written vs. generated, implementation pattern: single hand-written dispatch tool and error handling (mandatory).