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/ShekharBhardwaj/AgenticLedgerWrote 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/shekharbhardwaj/agenticledger/agentic-ledger)<a href="https://agentmods.dev/mcp/shekharbhardwaj/agenticledger/agentic-ledger"><img src="https://agentmods.dev/badge/mcp/shekharbhardwaj/agenticledger/agentic-ledger.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agentic-ledger 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 7d 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
{
"agentic-ledger": {
"command": "uvx",
"args": [
"agentic-ledger"
],
"env": {}
}
}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.
- 7d ago First seen · 9 lines scan A babc2dc7f1ee
agentic-ledger is an MCP server published in the GitHub repository ShekharBhardwaj/AgenticLedger (5 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
llmkit
AI cost tracking: 11 tools for spend, budgets, and Claude Code + Cursor + Cline costs. Runs locally from the @f3d1/llmkit-mcp-server npm package. Needs 2 environment variables to run.
beezi
MCP server "beezi" as configured in Beezi-AI/beezi-claude-plugin. Runs ${CLAUDE_PLUGIN_ROOT}/scripts/mcp.mjs with node.
agent-cost-mcp
Cost Guard for Claude Code: per-tool ROI, subagent attribution, anomaly/forecast/budget guards. Runs locally from the @vk0/agent-cost-mcp npm package.
acr
Interaction profile registry for AI agents. Log interactions, query behavioral lenses. Runs locally from the @tethral/acr-mcp npm package. Needs 1 environment variable to run.
spend
See what every AI agent costs you, across every vendor, in one line. No account, no dependencies, no network calls. Runs locally from the focxle Python package. Needs 1 environment variable to run.
llm-cost-guard
Track LLM costs, set budget limits, get alerts. One command to install, one line to use. Runs locally from the @wimoron/llm-cost-guard npm package.