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/kalcifield/ovf-data-mcp/agents-mdgit clone --depth 1 https://github.com/kalcifield/ovf-data-mcpWrote 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/kalcifield/ovf-data-mcp/agents-md)<a href="https://agentmods.dev/instructions/kalcifield/ovf-data-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kalcifield/ovf-data-mcp/agents-md.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.00614 | $0.00614 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
ovf-data-mcp 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 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Python code uses the src layout under src/vizugy/. Keep stable domain models in
models.py, intent-level workflows in service.py, and upstream details in
providers.py (ArcGIS) or vra_provider.py (VRAQuery). cli.py and mcp_server.py
must remain thin adapters over the same service methods. Tests live in tests/ and
follow the corresponding capability, for example test_vra_provider.py and
test_investigation.py. Design findings and verified upstream behavior belong in
docs/. See README.md for the public interface.
Build, Test, and Development Commands
Use Python 3.11+ and uv:
uv sync --extra test # install runtime and development dependencies
uv run vizugy --help # inspect or run the CLI
uv run ovf-data-mcp # start the stdio MCP server
uv run pytest -q # run deterministic tests and MCP smoke tests
uv run ruff format --check src tests
uv run ruff check src tests
uv run mypy src tests
Run uv run pre-commit run --all-files before submitting broad changes.
Release: scripts/release {patch|minor|major}; GitHub Actions publishes to PyPI asynchronously.
Coding Style & Naming Conventions
Use four-space indentation, Python type annotations, and Ruff formatting. Modules,
functions, and variables use snake_case; classes and Pydantic models use
PascalCase. Prefer small typed domain objects over leaking upstream Hungarian field
names. Preserve raw provider semantics inside adapters. CLI/MCP outputs must keep data
on stdout and diagnostics on stderr.
Testing Guidelines
Tests use pytest, pytest-asyncio, httpx.MockTransport, and recorded deterministic
responses. Name tests test_<behavior>. Cover normalization, bounds, ambiguity,
upstream errors, compact output, and CLI/MCP parity. Routine tests must not require live
OVF services; use small live probes only for explicit contract validation. No numeric
coverage threshold is currently enforced.
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 · 60 lines · 614 tokens per session scan A 33a12323fe11
ovf-data-mcp AGENTS.md is an instructions file published in the GitHub repository kalcifield/ovf-data-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 614 tokens to every session, about $0.0031 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.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
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.