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/automagik-dev/forgeWrote 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/automagik-dev/forge/genie)<a href="https://agentmods.dev/mcp/automagik-dev/forge/genie"><img src="https://agentmods.dev/badge/mcp/automagik-dev/forge/genie/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/automagik-dev/forge/genie"><img src="https://agentmods.dev/badge/mcp/automagik-dev/forge/genie.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
genie 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 1mo 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
{
"genie": {
"command": "npx",
"args": [
"-y",
"automagik-genie@next",
"mcp"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 10 lines scan A 0d1b78486202
genie is an MCP server published in the GitHub repository automagik-dev/forge (92 stars, last pushed 10mo ago), licensed Apache-2.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
chrome
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
capsule
Compact, source-linked context packs that reduce token waste for coding agents. Runs locally from the capsulectx npm package.
semaphore
MCP server "semaphore" as configured in alwh1te/agent-semaphore. Launched with asem mcp.
repo-guard
Executable policy engine for coding agents: gate what touches your repo (paths, contents, commands), not just tool names. MCP server + CLI + hooks. Runs locally from the @darkm3tter/repo-guard npm package.
context7
Context7's hosted MCP server: up-to-date library documentation and code examples on demand. Remote server at mcp.context7.com.
cartograph
Declarative MCP server for the Cartograph widget library. Runs locally from the cartograph-mcp Python package.