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/omarkhandji-commits/midasWrote 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/omarkhandji-commits/midas/midas-agent)<a href="https://agentmods.dev/mcp/omarkhandji-commits/midas/midas-agent"><img src="https://agentmods.dev/badge/mcp/omarkhandji-commits/midas/midas-agent.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
midas-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 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.
What it actually says
{ "midas-agent": { "command": "uvx", "args": [ "midas-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.
- 7d ago First seen · 8 lines scan A ccf708d21164
midas-agent is an MCP server published in the GitHub repository omarkhandji-commits/midas (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
termlink
MCP server "termlink" as configured in DimitriGeelen/agentic-engineering-framework. Launched with termlink mcp serve. Needs 1 environment variable to run.
skills
MCP server "skills" as configured in DimitriGeelen/agentic-engineering-framework. Runs /opt/150-skills-manager/skills-mcp-server/server.py with python3.
fw
MCP server "fw" as configured in DimitriGeelen/agentic-engineering-framework. Runs agents/mcp/framework_mcp_server.py with python3.
sidclaw-governance-mcp
Governance proxy for MCP servers — policy evaluation, human approval, audit trails. Runs locally from the @sidclaw/sdk npm package. Needs 5 environment variables to run.
glitchtip
MCP server "glitchtip", hosted remotely at glitchtip.infra.developerz.ai, as configured in developerz-ai/ai-task-master.
synartesis
An undo layer for AI agents. Runs locally from the synartesis npm package.