Borrowing it
Nothing to install: this file belongs to bitflight-devops/mcp-json-yaml-toml. 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/bitflight-devops/mcp-json-yaml-toml/main/AGENTS.mdgit clone --depth 1 https://github.com/bitflight-devops/mcp-json-yaml-tomlWrote 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/bitflight-devops/mcp-json-yaml-toml/agents-md)<a href="https://agentmods.dev/instructions/bitflight-devops/mcp-json-yaml-toml/agents-md"><img src="https://agentmods.dev/badge/instructions/bitflight-devops/mcp-json-yaml-toml/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/bitflight-devops/mcp-json-yaml-toml/agents-md"><img src="https://agentmods.dev/badge/instructions/bitflight-devops/mcp-json-yaml-toml/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.01172 | $0.01172 |
| Opus 5.5 | $0.00469 | $0.00469 |
| Sonnet 5.5 | $0.00234 | $0.00234 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
mcp-json-yaml-toml 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 1mo 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP JSON/YAML/TOML Server - AI Agent Instructions
AI agents working in this repository follow these instructions for consistency, quality, and architectural integrity.
Project Context
Purpose: MCP server for advanced JSON/YAML/TOML manipulation using yq
Stack: Python 3.11-3.12+, FastMCP, uv, hatchling
Core Components:
yq_wrapper.py- Local binary managementschemas.py- Schema discoverylmql_constraints.py- LMQL constraint validation
Design Principles:
- 100% local processing (no API keys required)
- High-fidelity format preservation (comments, anchors, whitespace)
- Unified tools with parameters (avoid tool proliferation)
- Cursor-based pagination (10KB chunks for large files)
Linting Philosophy
<linting_principles>
Linting errors indicate deeper issues in architecture, type flow, or logic. Address root causes rather than suppressing symptoms.
Resolution Hierarchy:
- Structural/type problems → Fix architecture or type annotations
- Formatting/style → Use automated tools (
ruff format,prettier) - True false positives → Document why before suppressing
Suppression Usage:
- Acceptable: Vendored code, intentional examples, platform-specific constraints
- Unacceptable: Structural problems, type errors, logic issues
Reason: Suppressions (# type: ignore, # noqa) hide technical debt. Fixing root causes improves system health.
</linting_principles>
Development Workflow
Environment Setup
uv sync # Install dependencies and dev-tools
Dependency Management
uv add <package> # Add runtime dependency
uv add --dev <package> # Add dev dependency
uv remove <package> # Remove dependency
uv add/remove handles version resolution, lockfile updates, and installation atomically. Manual pyproject.toml edits bypass dependency resolution and cause inconsistent environments.
Verification Protocol
<verification_workflow>
After editing files, verify only changed files (surgical verification prevents diff pollution):
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.
- 1mo ago Changed · -1 lines · -28 tokens per session 69a629fa16c2
- 2mo ago First seen · 188 lines · 1,200 tokens per session scan A ee0daaf3c1ea
mcp-json-yaml-toml AGENTS.md is an instructions file published in the GitHub repository bitflight-devops/mcp-json-yaml-toml (10 stars, last pushed yesterday), licensed MIT. It adds 1,172 tokens to every session, about $0.0047 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-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).
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.