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.
git clone --depth 1 https://github.com/alex-jb/build-quality-agentWrote 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/alex-jb/build-quality-agent/build-quality-agent)<a href="https://agentmods.dev/mcp/alex-jb/build-quality-agent/build-quality-agent"><img src="https://agentmods.dev/badge/mcp/alex-jb/build-quality-agent/build-quality-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/alex-jb/build-quality-agent/build-quality-agent"><img src="https://agentmods.dev/badge/mcp/alex-jb/build-quality-agent/build-quality-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
build-quality-agent 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 9d 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
{ "build-quality-agent": { "command": "uvx", "args": [ "build-quality-agent" ] } }
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.
- 9d ago First seen · 8 lines scan A 3d86e1bb54b0
build-quality-agent is an MCP server published in the GitHub repository alex-jb/build-quality-agent (1 stars, last pushed 2mo 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
argot
Flags code foreign to your repo's patterns, learned from git history. Local; statistics, no LLM. Runs locally from the @tmonier/argot npm package.
totem
MCP server "totem" as configured in mmnto-ai/totem. Launched with cmd /c npx -y @mmnto/mcp.
github
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
juror
MCP server "juror", hosted remotely at app.juror.dev, as configured in Juror-AI/juror.
git-a2a
Git module dependencies and owning-agent routing for coding agents. Runs locally from the git-a2a npm package.
code-review-graph
Local-first knowledge graph for token-efficient code review through MCP and CLI. Runs locally from the code-review-graph Python package.