ledger-metering

A plugin that records Claude Code token usage in a self-hosted Ledger dashboard, a private system for tracking usage and costs.

In plain words
What is it for?
Use it to meter each session's token usage and compare its API-equivalent value with actual cost.
Why use it?
It lets you review spending and efficiency without sending the conversation transcript; only token-related metadata is sent.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add Perseus-Computing-LLC/ledger
agentmods
npx agentmods add plugins/perseus-computing-llc/ledger/claude-code-plugin
Clone the repo
git clone --depth 1 https://github.com/Perseus-Computing-LLC/ledger

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

ledger-metering 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 yesterday.

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.

integrations/claude-code-plugin/.claude-plugin/plugin.json · 11 lines

What it actually says

{
  "name": "ledger-metering",
  "description": "Meter Claude Code token usage to your self-hosted Ledger ledger. Each turn's usage is metered at session end so you can see your spend and efficiency (API-equivalent value vs. actual cost) on the Ledger dashboard. Sends token metadata only — never transcript content.",
  "version": "0.1.0",
  "author": { "name": "Perseus Computing LLC", "url": "https://perseus.observer" },
  "homepage": "https://github.com/Perseus-Computing-LLC/ledger-metering-plugin",
  "repository": "https://github.com/Perseus-Computing-LLC/ledger-metering-plugin",
  "license": "MIT",
  "keywords": ["metering", "billing", "cost", "token-usage", "finops", "ledger"]
}
Changes

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.

  1. yesterday First seen · 11 lines scan A 2ec5b76e2e63

Subscribe to this mod's changes

ledger-metering is a plugin published in the GitHub repository Perseus-Computing-LLC/ledger (5 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.