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.
npx agentmods add mcp/ashlrai/ashlr-plugin/ashlrgit clone --depth 1 https://github.com/ashlrai/ashlr-pluginGrade A, and why
ashlr 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 2d 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
{
"ashlr": {
"command": "ashlr-mcp",
"args": [],
"cwd": ".",
"env": {
"ASHLR_MCP_HOST": "codex-cli",
"ASHLR_CODEX_HOOK_MODE": "nudge"
},
"instructions": "Prefer Ashlr tools when they reduce context: use ashlr__read for large files, ashlr__grep for search, ashlr__tree for directory maps, ashlr__bash for verbose shell output, ashlr__savings for token/cost accounting, and ashlr__genome_* tools for project memory. Pass cwd explicitly or set ASHLR_ALLOW_PROJECT_PATHS for workspaces outside the MCP launch 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.
- 2d ago First seen · 12 lines scan A 486ab60cffd7
ashlr is an MCP server published in the GitHub repository ashlrai/ashlr-plugin (3 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
bun-docs
MCP server "bun-docs", hosted remotely at bun.com, as configured in stefanprodan/cctop.
attack-surface-mcp-server
Passive external attack-surface mapping: CT subdomains, DNS, TLS, HTTP posture, RDAP/WHOIS, Shodan. Runs locally from the @cyanheads/attack-surface-mcp-server npm package. Needs 8 environment variables to run.
usda-mcp-server
Search foods, compare nutrients, and look up the full USDA FoodData Central database. Runs locally from the @cyanheads/usda-mcp-server npm package. Needs 2 environment variables to run.
session-control
MCP server "session-control" as configured in project-tharsis/claude-code-telegram-kit. Launched with /home/USER/.bun/bin/bun run /home/USER/.local/share/claude-code-telegram-kit/cur. Needs 4 environment variables to run.
sentry
Sentry's hosted MCP server: lets the agent search and read issues, errors and traces. Remote server at mcp.sentry.dev.
agora-mcp
Shared per-repo space for Claude Code sessions: see activity, get collision warnings, notes. Runs locally from the @vorluno/agora-mcp npm package.