Individual skill

hermes-token-audit

Use when Hermes token usage, cost attribution, runaway sessions, cron consumption, or billing discrepancies must be investigated using privacy-preserving, schema-aware evidence.

skills/hermes-token-audit/SKILL.md

Read pinned source

Source commit 367f8a35ff4703cec722b0678ad853814032ba7f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
127
Repository last updated
Oct 26, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# hermes-token-audit

## Overview

A read-only, schema-discovering token and cost audit that defaults to aggregate metadata and clearly separates local estimates from provider billing.

The skill is evidence-first. It identifies unavailable evidence, separates facts from interpretations, and does not claim a repair or successful outcome merely because a command returned without an obvious error.

## When to Use

- Where did my Hermes tokens go?
- Which sessions cost the most?
- Did a cron job burn the budget?
- Why does provider billing not match local usage?