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/jyswee/buggaziWrote 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/jyswee/buggazi/buggazi)<a href="https://agentmods.dev/mcp/jyswee/buggazi/buggazi"><img src="https://agentmods.dev/badge/mcp/jyswee/buggazi/buggazi.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
buggazi 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 7d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 7d ago First seen · 13 lines scan A 922e7c8add4b
buggazi is an MCP server published in the GitHub repository jyswee/buggazi (1 stars, last pushed 8d ago), with no licence file. 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
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package.
audit
Score any public GitHub repo 0-100 against the commit.show audit rubric. Runs locally from the commitshow-mcp npm package.
cli
A local-first registry of every project on your machine, exposed to your coding agents via MCP. Runs locally from the @itacajs/cli npm package.
warmstart
Self-verifying operational manifest for coding agents. npx warmstart init. Runs locally from the warmstart npm package.
mcp-lint
Lint MCP tool schemas for cross-client compatibility and agent preflight safety. Runs locally from the mcp-lint npm package.
keshro-mcp
High-stakes engineering project execution for AI agents — MCP server. Runs locally from the keshro-mcp Python package.