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/vakra-dev/atom-cliWrote 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/vakra-dev/atom-cli/cli)<a href="https://agentmods.dev/mcp/vakra-dev/atom-cli/cli"><img src="https://agentmods.dev/badge/mcp/vakra-dev/atom-cli/cli/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/vakra-dev/atom-cli/cli"><img src="https://agentmods.dev/badge/mcp/vakra-dev/atom-cli/cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cli 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 1mo 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
{ "cli": { "command": "npx", "args": [ "-y", "@useatom/cli" ] } }
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.
- 1mo ago First seen · 9 lines scan A cc2e7a06783b
cli is an MCP server published in the GitHub repository vakra-dev/atom-cli (0 stars, last pushed 1mo 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
okffs
MCP server connecting Claude Code to GitHub for an issue to branch to PR to close workflow. Runs locally from the @neturely/okffs npm package. Needs 3 environment variables to run.
obsidian-github-mcp
MCP server "obsidian-github-mcp" as configured in SarutobiSasuke8/obsidian-github-mcp. Runs locally from the @sarutobi-sasuke/obsidian-github-mcp npm package.
semver-checks
Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump. Runs locally from the semver-checks npm package.
binky
Give every git worktree its own isolated local world — ports, env, database, URLs — so a swarm of agents runs in parallel without collisions. Runs locally from the binky Python package.
rea
Reverse engineer anything from your terminal or agent with one CLI and MCP server. Runs locally from the rea-agents npm package.
bls-mcp
MCP server "bls-mcp", hosted remotely at 127.0.0.1, as configured in openai/openai-cookbook.