Borrowing it
Nothing to install: this file belongs to tuva-health/tuva-core. 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/tuva-health/tuva-core/main/AGENTS.mdgit clone --depth 1 https://github.com/tuva-health/tuva-coreWrote 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/tuva-health/tuva-core/agents-md)<a href="https://agentmods.dev/instructions/tuva-health/tuva-core/agents-md"><img src="https://agentmods.dev/badge/instructions/tuva-health/tuva-core/agents-md/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/tuva-health/tuva-core/agents-md"><img src="https://agentmods.dev/badge/instructions/tuva-health/tuva-core/agents-md.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.04808 | $0.04808 |
| Opus 5.5 | $0.01923 | $0.01923 |
| Sonnet 5.5 | $0.00962 | $0.00962 |
| Haiku 4.5 | $0.00481 | $0.00481 |
Grade A, and why
tuva-core AGENTS.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 20d 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 — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tuva Core Agent Operating Manual
Read and follow this file before changing Tuva Core, including from a linked worktree. It is the repository-local source of truth for ownership, safety, validation, CI, and release rules.
Tuva Core 1.0 Contract
- The repository is
tuva-health/tuva-core. - The dbt project name remains
the_tuva_projectfor package compatibility. dbt_project.ymldeclares version1.0.0and requires dbt 1.10.5 through 2.x. The complete 1.0 package ecosystem is validated against dbt Core 2.0 and dbt Fusion on DuckDB.- Repository
mainis the active integration line. A version onmainis not a formal release by itself. A release also requires an immutablev<version>tag and a GitHub release. - Treat published model schemas, grains, identifiers, variables, selectors, and stable Data Quality interfaces as public contracts. Assume a change is breaking unless compatibility is demonstrated.
- Use
v0.18.0only as the frozen pre-1.0 parity baseline. Never use a mutable branch as a release comparison baseline.
Repository Boundaries
Tuva Core owns the common transformation path:
- Input Layer contracts in
models/input_layer. - Standardization and terminology normalization in
models/normalized_layer. - Service categories, encounters, member months, claims enrollment, and
provider attribution in
models/claims_preprocessing. - Public common-model outputs in
models/core. - Opt-in Structural Data Quality and Logical Data Quality models in
models/data_quality. - Package metadata in
models/metadata. - The opt-in parity metric producer in
models/parity. - Core-owned seed headers and loader macros in
seedsandmacros.
Tuva Core does not own optional marts or extensions. The accepted 1.0 standalone packages are:
ahrq_quality_indicatorsccsrcms_chronic_conditionscms_hccfhir_preprocessingnyu_ed_classificationquality_measuressemantic_layerin repositorysemantic-layer
Installing a standalone package is its package-level enablement. Each package owns its models, tests, data assets, documentation, compatibility, and release lifecycle. Do not move optional-package code back into Core.
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.
- 20d ago Changed · +7 lines · +156 tokens per session b9885559ac33
- 1mo ago Changed · +7 lines · +96 tokens per session 4ff58f340cf8
- 1mo ago Changed · +23 lines · +312 tokens per session 4886d26a5e36
- 2mo ago First seen · 433 lines · 4,244 tokens per session scan A 672d132fe541
tuva-core AGENTS.md is an instructions file published in the GitHub repository tuva-health/tuva-core (333 stars, last pushed yesterday), licensed Apache-2.0. It adds 4,808 tokens to every session, about $0.0192 per session on Opus 5.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
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.