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/RyanAlberts/best-of-Agent-HarnessesWrote 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/ryanalberts/best-of-agent-harnesses/agent-harnesses)<a href="https://agentmods.dev/mcp/ryanalberts/best-of-agent-harnesses/agent-harnesses"><img src="https://agentmods.dev/badge/mcp/ryanalberts/best-of-agent-harnesses/agent-harnesses/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/ryanalberts/best-of-agent-harnesses/agent-harnesses"><img src="https://agentmods.dev/badge/mcp/ryanalberts/best-of-agent-harnesses/agent-harnesses.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-harnesses 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 12d 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
Licensed CC-BY-SA-4.0
The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 12d ago First seen · 9 lines scan A d30c197bd089
agent-harnesses is an MCP server published in the GitHub repository RyanAlberts/best-of-Agent-Harnesses (843 stars, last pushed 2d ago), licensed CC-BY-SA-4.0. 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-30.
Other mcp servers, from other repositories
cdp
MCP server "cdp" as configured in Lykhoyda/rn-dev-agent. Runs const f=require('fs'),p=require('path'),o=require('os'),c=require('child_process');const V='1.0.8';const D=x=>{try{return f.readdirSync(x).map(n=>p.join(x,n)).filter(z=>{try{return f.statSync(z).isDirectory()}catch{return false}})}catch{return[]}};const…
upwork
MCP server "upwork", hosted remotely at 127.0.0.1, as configured in citizenweb3/upwork-agent.
context-book-mcp
Stop re-explaining yourself to Agents. Give it the right context, right when needed. Remote server at context-book-mcp-production.up.railway.app.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm run start-stdio.