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/aahlijia/dekkoWrote 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/aahlijia/dekko/claude-dekko)<a href="https://agentmods.dev/mcp/aahlijia/dekko/claude-dekko"><img src="https://agentmods.dev/badge/mcp/aahlijia/dekko/claude-dekko/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/aahlijia/dekko/claude-dekko"><img src="https://agentmods.dev/badge/mcp/aahlijia/dekko/claude-dekko.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dekko 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 9d 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
{
"dekko": {
"command": "dekko",
"args": [
"serve",
"--mcp"
],
"cwd": "${CLAUDE_PROJECT_DIR}"
}
}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.
- 9d ago First seen · 10 lines scan A 4a3c11625923
dekko is an MCP server published in the GitHub repository aahlijia/dekko (3 stars, last pushed 8d 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
roam-code
MCP server "roam-code" as configured in Cranot/roam-code. Launched with roam mcp. Needs 1 environment variable to run.
codeweb
Your agents break less code and burn fewer tokens — a deterministic call graph over 27 MCP tools. Runs locally from the @ghostlygawd/codeweb npm package.
symbiote
Symbiote bonds with your AI tools — giving them memory, context, and your coding DNA. Runs locally from the symbiote-cli npm package.
graftmap
Local-first codebase context engine for AI coding tools. Runs locally from the graftmap npm package.
stockbit-mcp
Indonesian exchange (IDX) via your own Stockbit account: quotes, bandarmology, charts. Unofficial. Runs locally from the stockbit-mcp npm package. Needs 4 environment variables to run.
aptu-coder
MCP server "aptu-coder" as configured in clouatre-labs/aptu-coder. Launched with aptu-coder.