agentmods.dev

chart-contract AGENTS.md

Project instructions for chart-contract, a Python tool that checks whether analytical charts support their claims, data, visual choices, sources, and caveats.

In plain words
What is it for?
They guide work on the project while preserving its defined scope, deterministic audit rules, verification notes, and handoff documentation.
Why use it?
They help prevent misleading charts, unsupported causal claims, hidden data changes, and unexplained warnings.

Instructions file for CodexOpenCode

2 8d ago A scan 193 tokens original MIT
View the source file tmusser/chart-contract
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/tmusser/chart-contract/agents-md
Clone the repo
git clone --depth 1 https://github.com/tmusser/chart-contract

Made for: Codex, OpenCode.

Per session 193 This file is loaded in full into every session.
When invoked 193 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.00193 $0.00193
Opus 5 $0.00097 $0.00097
Sonnet 5 $0.00039 $0.00039
Haiku 4.5 $0.00019 $0.00019

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

Security

Grade A, and why

chart-contract 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 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.

AGENTS.md · 14 lines

What it actually says

AGENTS.md

  • Preserve the v0.1 scope in artifacts/SPEC.md.
  • Do not add UI, dashboards, or extra chart types without updating artifacts/SPEC.md.
  • Prefer deterministic audit rules over vague judgment.
  • Keep warnings explainable.
  • Do not claim causality unless evidence supports it.
  • Do not mutate or fetch external data.
  • Do not silently truncate quantitative scales or normalize values. For external Vega-Lite specs, require explicit usermeta.user_requested_scale_override=true or usermeta.user_requested_normalization=true before those transformations can pass the policy audit.
  • Treat user-request metadata as a declaration, not proof that the user actually requested the transformation.
  • A truncated quantitative bar baseline remains a visual-integrity failure even when user-request metadata is present.
  • Update artifacts/VERIFY.md after changes.
  • Update artifacts/HANDOFF.md before ending a session.
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 · 14 lines · 193 tokens per session scan A bb4c9742914d

Subscribe to this mod's changes

chart-contract AGENTS.md is an instructions file published in the GitHub repository tmusser/chart-contract (2 stars, last pushed 8d ago), licensed MIT. It adds 193 tokens to every session, about $0.0010 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-31.

Analytics and metricsLanguagesWriting and docsai-agentsaltairdata-qualitydata-sciencedata-visualization
Related

Other instructions, from other repositories

marimo AGENTS.md

Instructions for marimo-team/marimo, covering marimo development guidelines, your primary responsibility is to the project and its users, quick setup, development commands and python.

marimo-team/marimo · 644 tokens

streamlit copilot-instructions.md

Copilot instructions for streamlit/streamlit, covering streamlit repo overview, tech stack, folder structure, shell & build policy and make commands.

streamlit/streamlit · 2,238 tokens

marimo copilot-instructions.md

Instructions for marimo-team/marimo: For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view and edit-view? For a backend change, has the user tested different scenarios?

marimo-team/marimo · 91 tokens

cnsplots AGENTS.md

Instructions for faridrashidi/cnsplots, covering agents.md, working branch rules, implementation rules, validation rules and commit rules.

faridrashidi/cnsplots · 1,376 tokens

streamlit python_tests.instructions.md

Instructions for streamlit/streamlit, covering python unit test guide, key principles, running tests and typing tests.

streamlit/streamlit · 784 tokens

streamlit agents.instructions.md

Instructions for streamlit/streamlit, covering agent definitions, file format, best practices, cross-platform compatibility and slash command support.

streamlit/streamlit · 832 tokens