by mikehasa
See what your coding agents did and what it cost. Breaks each task down into work steps — tools used, files changed, tests run, time and tokens spent. Local-first dashboard for Claude Code, Codex, OpenCode, and more. No login, no telemetry.
# Add to your Claude Code skills
git clone https://github.com/mikehasa/agentacctLast scanned: 7/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-07-30T06:26:36.513Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how agentacct compares with popular alternatives.
agentacct is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by mikehasa. See what your coding agents did and what it cost. Breaks each task down into work steps — tools used, files changed, tests run, time and tokens spent. Local-first dashboard for Claude Code, Codex, OpenCode, and more. No login, no telemetry. It has 718 GitHub stars.
Yes. agentacct passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/mikehasa/agentacct" and add it to your Claude Code skills directory (see the Installation section above).
agentacct is primarily written in Python. It is open-source under mikehasa on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh agentacct against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
See what your coding agents actually did — and whether you can trust it — as one honest Work Receipt per task, across Claude Code, Codex, OpenCode, and Hermes, without any of it leaving your machine.
agentacct is local-first Agent Work Intelligence for coding agents. It reads the session logs your agents already write on disk — Claude Code, Codex, OpenCode, and Hermes — joins them with the work each session records as it goes, and turns the result into one honest Work Receipt per task: what it did (the commands it ran, the files it touched, the tools it used), what it cost, and how well that is actually proven. Each receipt reads like an audit record, not a vibe: the decision ("the agent says it's done") and the evidence ("a machine check proves it") are separate axes, and every evidence tier has its own shape — an agent's claim can never dress up as verification. See it in the macOS app, a live terminal dashboard (agentacct tui), or over a local JSON API. No browser tab, no hosted server, no account.

Private by design. Everything stays on your machine: state is plain local files, the only listener is a loopback-only local JSON API (127.0.0.1) that onboarding starts and agentacct stop stops, and there is no phone-home telemetry, no account, no cloud sync. agentacct never stores or requests a provider API key.
Screenshots show a synthetic demo workspace; your own dashboard renders your machine's real local data.
The Work Receipt above is the whole product — the same Task-primary view lives in the macOS app, in agentacct tui (a live terminal dashboard), and over a local JSON API, across all four agents, in light and dark:
One Work Receipt per task — what it did, and whether you can trust it. Open a task and it reads like an audit record, not a vibe (that's the screenshot at the top): what it was, who ran it, the actions it took (commands run, files touched, tools used — read straight from each agent's own store and broken down by type), what it cost (with its basis — never an invoice), and the evidence — how much of the work carries a real passing check, where each fact came from, and whether anything external verified it. Decision and evidence are deliberately separate axes: an agent reporting done files under Reported and never raises the evidence bar, and a task only reads Verified when every live check passes and postdates the newest recorded work. Most fields wear a provenance chip — a client hook, a transcript scan, or the agent's own MCP records. Read one in the app, or with agentacct receipt <task>.
The work, not just the tokens. Each task rolls up into its sessions and the steps the agent recorded as it went. Open the drill-down for every step, its lifecycle (completed, handed off, blocked, or still in progress), its evidence-tier pip, and its checks — with exit codes and honest provenance. A passing check the agent reported for itself is labelled the agent's own, not independent, never dressed up as verification; the checks ledger leads with current failures, folds routine checks behind a Show N more control, and keeps superseded history separate.

Evidence tiers, not vibes. Every check is graded by how independent it is of the agent that did the work: an agent's own claim < a self-reported check < a hook-observed exit code < CI. The tier travels as a pip shape everywhere (hollow → half → filled → ringed), and green is reserved for live connections and externally verified evidence. A Sources pane keeps the store honest about what it can't yet verify — a CI-check-run and human-review shelf that reads not connected until independent evidence actually lands.
A receipts workbench. Every task your agents touch becomes a row you can hold them to: lifecycle tabs that never inflate a claim (Verified stays reserved for machine-checked completion), an evidence column whose pip shape carries the tier, a checks column with real pass/fail tallies, and a cost column where every figure wears its basis (≈ marks an estimate — a bare $ is reserved for reported figures). Sorted latest-first, with an attention-first sort one click away when the one blocked task should outrank nine finished ones.

A home that opens with what needs review. The Dashboard is an evidence-first Shift Brief: it names the single highest-priority task that needs review — its recorded reason, when it was observed, and where the claim came from — with a Review evidence button that opens the task in Work and a Copy review brief action that copies only the recorded facts (it never resumes or reruns the task). Beside it, a Signal rail carries four truth-bounded facts — Working now, Capacity, Usage change, and Evidence trust — each rendering an explicit unavailable state instead of a confident number when its data is missing, stale, or out of range.

Usage and plan cost in one decision view. Provider-reported quota windows and reset times sit beside each agent's independently ranged recorded usage; daily history and per-model attribution follow below. Tokens come from the clients' local session files and costs keep their reported/estimated/partial basis — never an invoice or a fabricated zero. agentacct also estimates what fraction of your weekly Claude plan each task consumed — learned from your own recorded limit history and shown only once it can calibrate to your account, always labelled an estimate.

Attribution you can trust. Every join between usage and recorded work carries a confidence label (exact/high/medium/low). Missing attribution beats wrong attribution: when agentacct cannot prove a link, it shows the gap instead of a guess — absence is always a named state, never a dash or a fabricated zero.
The signed, notarized macOS app bundles everything. Download the .dmg from the latest release, drag agentacct to Applications, and open it — first launch offers one-click setup of the bundled CLI and the coding agents it finds, then shows your Work Receipts in a native window. Requires macOS 14+.
Before its first local data request on each packaged-app launch, agentacct validates the embedded CLI and any App-owned installed copy. When the bundle contains a newer verified CLI, the App stages it as a complete immutable version, atomically retargets the stable launcher, and preserves the previous files for already-running MCP and hook processes; it never overwrites their CLI directory in place or takes over a user-managed/pipx install. This App/CLI sync is implemented and tested. In-App downloads and installation through Sparkle are still planned, not shipped; see the packaging notes for the exact layout and recovery boundary.
Requires Python >= 3.11 on macOS or Linux; Windows is supported only via WSL.
pipx install agentacct
agentacct onboard # once per machine (global by default)
agentacct tui # the live terminal dashboard
No pipx yet? Install it first with brew install pipx (macOS) or python3 -m pip install --user pipx — or skip pipx entirely and use uv tool install agentacct. See INSTALL.md for a plain-venv fallback.
onboard installs agentacct once per machine (global by default, writing zero files into your repo): it detects your local coding-agent logs, sets up a global s