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/vosesoftware/modelrisk-mcp/claude-mdgit clone --depth 1 https://github.com/vosesoftware/modelrisk-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/vosesoftware/modelrisk-mcp/claude-md)<a href="https://agentmods.dev/instructions/vosesoftware/modelrisk-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vosesoftware/modelrisk-mcp/claude-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.01077 | $0.01077 |
| Opus 5 | $0.00539 | $0.00539 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
modelrisk-mcp CLAUDE.md scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
After a tag pushes, watch the run with `gh run watch <id> --exit-status` and confirm all five jobs green. Then confirm the version appears on PyPI (`curl pypi.org/pypi/modelrisk-mcp/json | jq .info.version`) and on the M How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working preferences for Claude on this repo
Read this before doing work on modelrisk-mcp.
Git push policy
Always do git push yourself. Don't ask the user to switch to PowerShell and run it. The credential dialog works reliably from the bash/PowerShell shell Claude uses, provided the repo-local credential helper is set to manager:
git config --local credential.https://github.com.helper "manager"
That's already configured for modelrisk-mcp and shouldn't need to be re-set. If a push hangs, it's almost always Git Credential Manager waiting on the OS chooser — wait it out or check the user's screen for the dialog. Don't fall back to telling the user to push manually.
The standard sequence after a tagged commit:
git push origin main
git push origin <new-tag>
gh run watch <run-id> --repo vosesoftware/modelrisk-mcp --exit-status
Release pipeline (automated)
Pushing a tag v*.*.* or v*.*.*-* triggers .github/workflows/release.yml. Five jobs run, all green-or-fail:
build-wheel— wheel + sdist viauv buildbuild-windows-exe— PyInstaller exe + obfuscation scan (release-blocker)publish-pypi— wheel + sdist via OIDC trusted publishingpublish-mcp-registry—mcp-publishervia GitHub OIDC againstregistry.modelcontextprotocol.iogithub-release— assets attached to a GitHub Release page
After a tag pushes, watch the run with gh run watch <id> --exit-status and confirm all five jobs green. Then confirm the version appears on PyPI (curl pypi.org/pypi/modelrisk-mcp/json | jq .info.version) and on the MCP Registry.
Quality gate before every commit
Always run all three before committing. No exceptions:
.venv/Scripts/python.exe -m pytest tests/unit -q
.venv/Scripts/python.exe -m ruff check src tests scripts
.venv/Scripts/python.exe -m mypy src
mypy runs on src only — running it on tests/ surfaces a lot of test-time-only type: ignore lint noise that's not actionable.
Version bumping
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.
- 3d ago First seen · 75 lines · 1,077 tokens per session scan A d41f33503d66
modelrisk-mcp CLAUDE.md is an instructions file published in the GitHub repository vosesoftware/modelrisk-mcp (0 stars, last pushed 19d ago), licensed MIT. It adds 1,077 tokens to every session, about $0.0054 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.