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/maxgfr/conforme/adapter-consistencygit clone --depth 1 https://github.com/maxgfr/conformeWhat 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.00418 | $0.00418 |
| Opus 5 | $0.00209 | $0.00209 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
conforme adapter-consistency.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 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.
What it actually says
- Every adapter change MUST be reflected in its
docs/providers/<tool>.md - Every MCP format change MUST update the corresponding
generate_*_mcp_jsonfunction AND its unit test - When adding a new adapter, update ALL of: README.md tables, src/help_ai.rs, src/cli.rs tool count, CLAUDE.md architecture section
- Provider docs must list all official documentation URLs for the tool
- Test round-trips:
read()output fed intogenerate()should produce identical files - MCP JSON keys per tool: Claude/Windsurf/Kiro/RooCode/AmazonQ/Gemini/Cursor/Continue.dev =
mcpServers, Copilot =servers, OpenCode =mcp(insideopencode.json), Zed =context_servers, Amp =amp.mcpServers - OpenCode MCP specifics:
commandis a single array[cmd, ...args], env key isenvironment(notenv), servers live insideopencode.jsonat project root (conforme merges — never clobber user-authored keys) - Windsurf MCP specifics: no
typefield; HTTP transport usesserverUrl(noturl) - Amp MCP specifics: dotted
amp.mcpServerskey, notypefield, merged into.amp/settings.json(never clobber user settings) - Cursor subagents:
.mdextension (not.mdc); notoolsfrontmatter field — tool access is inherited from the parent agent - Copilot skills:
.github/skills/<name>/SKILL.md(NOT.github/prompts/*.prompt.md— prompt files are a separate VS Code feature) - Any adapter whose
generate()writes skills, agents, or MCP MUST read them back inread(), or--from <tool>silently drops them
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.
- 2d ago First seen · 17 lines · 418 tokens per session scan A 06f616e1f69a
conforme adapter-consistency.instructions.md is an instructions file published in the GitHub repository maxgfr/conforme (2 stars, last pushed 8d ago), licensed MIT. It adds 418 tokens to every session, about $0.0021 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
memorix GEMINI.md
Instructions for AVIDS2/memorix, covering memorix - cross-agent memory rules, session start - bind project, then load context, during session - capture important context, architecture & decisions and bug fixes & problem solving.
Ctxo CLAUDE.md
Instructions for alperhankendi/Ctxo, covering claude.md — ctxo, project overview, quick reference, dev (pnpm workspace) and usage (consumer).
anchor copilot-instructions.md
Instructions for peva3/anchor, covering github copilot instructions, required reading, critical rules, prohibited actions and project structure.
open-forge AGENTS.md
Instructions for zhangqi444/open-forge, covering agents.md, what this project is, working on this repo — the rules, build / test / lint and versioning.
Overture CLAUDE.md
Instructions for SixHq/Overture, covering claude.md, project overview, monorepo structure, build & development commands and install dependencies (from root).
ai-protocol AGENTS.md
Instructions for dnlbox/ai-protocol, covering agents.md, instruction format, instruction discovery, project truth and approved objectives.