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/geml-spec/gemlWrote 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/geml-spec/geml/codex-plugin-geml)<a href="https://agentmods.dev/mcp/geml-spec/geml/codex-plugin-geml"><img src="https://agentmods.dev/badge/mcp/geml-spec/geml/codex-plugin-geml/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/geml-spec/geml/codex-plugin-geml"><img src="https://agentmods.dev/badge/mcp/geml-spec/geml/codex-plugin-geml.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
geml 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 4d 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
{
"geml": {
"command": "npx",
"args": [
"-y",
"@geml/geml",
"mcp",
"--root",
"."
]
}
}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.
- 4d ago First seen · 12 lines scan A 2ae53ebd5d4c
geml is an MCP server published in the GitHub repository geml-spec/geml (29 stars, last pushed today), 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-10-12.
Other mcp servers, from other repositories
core
MCP server "core" as configured in asdecided/core. Runs in Docker (ghcr.io/asdecided/core:mcp-v0.29.0).
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Launched with sqry-mcp --no-daemon. Needs 1 environment variable to run.
ak-docs
Human↔agent documentation bridge — deterministic handoffs, doc-site links, memory→docs, optional AgentsKit RAG/chat. Runs locally from the @agentskit/doc-bridge npm package.
fonto-docs
Fonto (FontoXML) documentation for AI tools. Converts DITA XML to Markdown on demand. Remote server at fonto-docs.elliat.nl.
call-copilot
Call Copilot — silently record meeting audio in the background, then transcribe locally to clean markdown. Runs locally from the call-copilot Python package.
librarian
Deterministic book-to-markdown pipeline for LLM consumption. Runs locally from the librarian-cli Python package. Needs 1 environment variable to run.