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 mcp/dager23/repocontract/repo-contractgit clone --depth 1 https://github.com/dager23/RepoContractWrote 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/mcp/dager23/repocontract/repo-contract)<a href="https://agentmods.dev/mcp/dager23/repocontract/repo-contract"><img src="https://agentmods.dev/badge/mcp/dager23/repocontract/repo-contract.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
repo-contract 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 6d 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
{ "repo-contract": { "command": "uvx", "args": [ "repo-contract" ] } }
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.
- 6d ago First seen · 8 lines scan A 4d74d67f4d36
repo-contract is an MCP server published in the GitHub repository dager23/RepoContract (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
agent-guardrails
Local merge gates for AI coding agents with scope, validation, risk, and review evidence. Runs locally from the agent-guardrails npm package.
forensic-deepdive
Forensic deep-dive of any codebase (9 languages). Persistent code knowledge graph + MCP server (9 composite tools incl. hybrid NL query, Mermaid export & cross-stack trace) for AI coding agents, with 5 durable markdown artifacts (MAP, HOTPATHS, ARCHAEOLOGY, MENTALMODEL, AGENTBRIEF) as the human-readable projection.…
audit
Score any public GitHub repo 0-100 against the commit.show audit rubric. Runs locally from the commitshow-mcp npm package.
forgecraft
CLI + MCP sentinel for engineering standards — SOLID, testing, architecture, CI/CD — auto-tailored to your stack. Minimal MCP footprint (200 tokens) via CLI-first design. Runs locally from the forgecraft-mcp npm package.
pr-narrator-mcp
MCP server for generating consistent commit messages and PR content based on your custom criteria. Runs locally from the pr-narrator-mcp npm package.
code-quality
MCP server for code quality: complexity, duplicates, naming, refactoring. Runs locally from the sovereign-code-quality-mcp npm package.