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/testinggit 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.00098 | $0.00098 |
| Opus 5 | $0.00049 | $0.00049 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
conforme testing.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 yesterday.
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
- Integration tests use
assert_cmd+tempfilecrates - Each adapter must have round-trip tests in
tests/roundtrip.rs - MCP format tests belong in
src/mcp.rsunit tests - Error case tests go in
tests/error_cases.rs - Always assert on file paths AND content (not just existence)
- When changing an output path (e.g. MCP location), update ALL tests that reference it
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.
- yesterday First seen · 11 lines · 98 tokens per session scan A e1e257b8a75b
conforme testing.instructions.md is an instructions file published in the GitHub repository maxgfr/conforme (2 stars, last pushed 7d ago), licensed MIT. It adds 98 tokens to every session, about $0.0005 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
agents AGENTS.md
Instructions for scarletkc/agents, covering agent guidelines, environment, engineering principles, code style and testing.
codex-manager AGENTS.md
Instructions for ewsun22/codex-manager, covering codex manager 项目指令, 产品边界, 隐私与安全, 工程规则 and 开源文档与发布流程.
vibe-check AGENTS.md
Instructions for benavlabs/vibe-check, covering security rules, secrets, database, authentication and authorization and input and output.
Overture CLAUDE.md
Instructions for SixHq/Overture, covering claude.md, project overview, monorepo structure, build & development commands and install dependencies (from root).
open-forge CLAUDE.md
Instructions for zhangqi444/open-forge, covering claude.md, what is open-forge, architecture — 3 layers, asked in 3 questions, file layout for the 3 layers and a fourth orchestration layer — bundles.
harness-engineering CLAUDE.md
Instructions for jrenaldi79/harness-engineering, covering claude.md, project overview, core features, essential commands and testing.