hermes-report

A command that reads the .cc-forge/usage.log file and produces a structured report about project work and use of the cc-forge framework.

In plain words
What is it for?
Reviewing software-development progress, persona gate history, backlog movement, drift events, token use, and cc-forge observations. Run it when preparing information for a review.
Why use it?
It turns a raw usage log into an organised summary, so reviewing development progress and process history takes less manual effort.

Command

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.

agentmods
npx agentmods add commands/a-director/cc-forge/report
Clone the repo
git clone --depth 1 https://github.com/A-Director/cc-forge
Per session 66 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,580 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.01580
Opus 5 $0.00033 $0.00790
Sonnet 5 $0.00013 $0.00316
Haiku 4.5 $0.00007 $0.00158

Measured yesterday against content hash 19128bbb3475, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hermes-report 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.

commands/report.md · 184 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 184 lines · 66 tokens per session scan A 19128bbb3475

Subscribe to this mod's changes

hermes-report is a command published in the GitHub repository A-Director/cc-forge (2 stars, last pushed 2mo ago), with no licence file. It adds 66 tokens to every session and 1,580 once invoked, about $0.0003 per session on Opus 5. 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.