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/latitude-dev/latitude-llm/agentationgit clone --depth 1 https://github.com/latitude-dev/latitude-llmWrote 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/latitude-dev/latitude-llm/agentation)<a href="https://agentmods.dev/mcp/latitude-dev/latitude-llm/agentation"><img src="https://agentmods.dev/badge/mcp/latitude-dev/latitude-llm/agentation.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agentation 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
{
"agentation": {
"command": "npx",
"args": [
"-y",
"agentation-mcp",
"server"
]
}
}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 · 10 lines scan A 412156410430
agentation is an MCP server published in the GitHub repository latitude-dev/latitude-llm (4,619 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-08-30.
Other mcp servers, from other repositories
chrome-devtools
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.
mcpspend
Query your MCPSpend usage: cost today, top tools, recent sessions, budget projections. Runs locally from the @mcpspend/mcp-server npm package. Needs 2 environment variables to run.
agentlens
Tamper-evident, SHA-256 hash-chained audit trail and observability for AI agents. Runs locally from the @agentkitai/agentlens-mcp npm package.
agentic-ledger
Runtime observability for AI agents — see exactly what your agent did, why it did it, and what it cost. Runs locally from the agentic-ledger Python package.
skillfm-ai-health-token-usage-byok-cost-cleanup
AI health, token usage, LLM cost optimization, BYOK vault, and cleanup audits for MCP agents. Runs locally from the @skillfm/mcp npm package.
skillfm
AI health, token usage, LLM cost optimization, BYOK vault, and cleanup audits for MCP agents. Runs locally from the @skillfm/mcp npm package.