A command for recording a plain-language summary of a coding session. It asks the agent to inspect the project's documentation and project data before reporting what happened.

Use it after a coding session to document what was built, what worked, what went wrong, and which problems still need attention.

It helps create a session record based on actual tool and project results rather than memory or conversation alone. The report includes successes, failures, and discovered issues.

test — Command by rygel

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/rygel/aiusagetracker/test

Clone the repo

git clone --depth 1 https://github.com/rygel/AIUsageTracker

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 83 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00083
Opus 5	$0.00000	$0.00042
Sonnet 5	$0.00000	$0.00017
Haiku 4.5	$0.00000	$0.00008

Measured 2d ago against content hash 483009c9dd02, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test 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 2d ago.

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.

.claude/commands/test.md · 6 lines

What it actually says

You are filling in a test finding for this session. Read the docs/ directory for any test schema or guidelines first.

Then read your project data for context — use MCP tools (board_view, build_list, health) as the source of truth for what happened, not the conversation history.

Summarise the session: what was built, what went well, what went wrong, and any issues discovered.

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.

2d ago First seen · 6 lines · 0 tokens per session scan A 483009c9dd02

Subscribe to this mod's changes

test is a command published in the GitHub repository rygel/AIUsageTracker (44 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 83 tokens. 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-30.

antigravity claude-code github-copilot kimi opencode windows

test

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

optimize

review

project-scan

design

requirement

commit-msg