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 skills/maxgfr/conforme/verify-providersnpx skills add maxgfr/conforme --skill verify-providersgit clone --depth 1 https://github.com/maxgfr/conformeWrote 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/skills/maxgfr/conforme/verify-providers)<a href="https://agentmods.dev/skills/maxgfr/conforme/verify-providers"><img src="https://agentmods.dev/badge/skills/maxgfr/conforme/verify-providers.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.00018 | $0.00551 |
| Opus 5 | $0.00009 | $0.00275 |
| Sonnet 5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
verify-providers 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit every conforme provider adapter against the latest upstream documentation. For each of the 14 tools, follow these steps:
1. Read the adapter code and provider docs
For each tool (claude, cursor, copilot, windsurf, continuedev, kiro, amazonq, codex, opencode, gemini, zed, amp, roocode, deepseek):
- Read
src/adapters/<tool>.rs - Read
docs/providers/<tool>.md - Note the official doc URLs listed in the provider doc
2. Fetch the latest official documentation
Open each official documentation URL from docs/providers/<tool>.md with the
host's native web reader. On Claude Code this may be WebFetch; on Codex use
the available web browsing tool. If direct opening fails, search the official
vendor domain and open the replacement page.
Extract the current:
- Config file paths and names
- Frontmatter fields and their types
- Activation mode mappings
- Skills/agents/MCP format and file locations
- Any new features or breaking changes
3. Compare adapter code vs official docs
Check for discrepancies in:
- File paths: Are we writing to the correct locations?
- Frontmatter fields: Are we reading/writing all required fields? Using correct separators?
- MCP format: Correct JSON key (
mcpServers,servers,context_servers,amp.mcpServers,mcp)? Correct transport types? - Skills format: Correct frontmatter fields per tool?
- Agents format: Correct file extension and frontmatter?
- Activation modes: Correct mapping values?
4. Fix discrepancies
For each issue found:
- Fix the adapter code in
src/adapters/orsrc/mcp.rsorsrc/skills.rs - Update the provider doc in
docs/providers/ - Update
src/help_ai.rsif the help text is affected - Update tests in
tests/to match new behavior - Run
cargo testto verify
5. Verify links
Open each documentation URL to confirm it still resolves (not 404).
If a link is broken, search for the new URL and update docs/providers/<tool>.md.
6. Final checks
cargo test
cargo clippy -- -D warnings
cargo fmt -- --check
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 · 64 lines · 18 tokens per session scan A 315a6c819b80
verify-providers is a skill published in the GitHub repository maxgfr/conforme (2 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 551 once invoked, about $0.0001 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 skills, from other repositories
project-spine-kickoff
Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs spine init → edits brief → spine compile → reviews outputs. For stale files use…
project-spine
Use when the user mentions AGENTS.md, CLAUDE.md, copilot-instructions, Cursor rules, project brief, context for coding agents, agency kickoff, onboarding a new project, or asks "how do I set up Project Spine". This is the orientation skill — reach for it FIRST when the user's intent involves Project Spine, then chain…
project-spine-drift
Use when the user mentions drift, says AGENTS.md / CLAUDE.md / copilot-instructions / Cursor rules are "stale" or "out of date", asks about CI catching docs drift, or says "check if my spine is still current". Runs spine drift check, interprets each drift category, and guides resolution. For initial setup use…
project-spine-template
Use when the user wants to apply a bundled, user-local, or project-local template to a new project, or save the current project as a reusable template. Phrases like "use our agency starter", "save this as a template for future clients", "apply the shared saas-marketing starter".
project-spine-rationale
Use when the user wants to review, polish, or share the generated Project Spine rationale file locally. Phrases like "show the project rationale", "send the client a project summary", "review rationale.md", or "make the client-facing overview safer".
project-spine-workspace
Use when the user asks about Project Spine hosted workspaces, team sync, shared workspace templates, invites, or commands such as spine login, spine workspace, spine publish, or spine drift check --push.