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/moelomda/context-atlasWrote 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/moelomda/context-atlas/context-atlas-context-atlas)<a href="https://agentmods.dev/mcp/moelomda/context-atlas/context-atlas-context-atlas"><img src="https://agentmods.dev/badge/mcp/moelomda/context-atlas/context-atlas-context-atlas/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/moelomda/context-atlas/context-atlas-context-atlas"><img src="https://agentmods.dev/badge/mcp/moelomda/context-atlas/context-atlas-context-atlas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context-atlas 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 8d 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
{
"context-atlas": {
"command": "node",
"args": [
"./scripts/run-context-atlas-mcp.mjs"
],
"cwd": "."
}
}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.
- 8d ago First seen · 9 lines scan A a80bb253c1a9
context-atlas is an MCP server published in the GitHub repository moelomda/context-atlas (0 stars, last pushed 2d 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
gnosis
MCP server "gnosis" as configured in nicholasglazer/gnosis-mcp. Launched with gnosis-mcp serve.
git
Lets the agent read, search and manipulate local git repositories: log, diff, status, commit. Runs locally from the mcp-server-git Python package.
docgraph
MCP server "docgraph" as configured in Detective-XH/DocGraph. Launched with docgraph serve --path ..
livewiki
A repository wiki of Markdown pages anchored to real code: read, search, and verified writes. Runs locally from the @livewiki/mcp npm package.
repo-history
MCP server "repo-history" as configured in hr23232323/repo-history. Runs locally from the repo-history Python package.
veridge
The always-fresh, low-token map of a whole project — docs, code (to the symbol), decisions — ranked by what matters and served to AI and humans alike. Runs locally from the veridge Python package.