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.
Profile →npx skills add asimons81/hermes-field-kit --skill hermes-token-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. ## W
What does the hermes-token-audit skill do?
Use when Hermes token usage, cost attribution, runaway sessions, cron consumption, or billing discrepancies must be investigated using privacy-preserving, schema-aware evidence.
How do I install it?
Run `npx skills add asimons81/hermes-field-kit --skill hermes-token-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From asimons81/hermes-field-kit, a repository with 120 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.