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.
git clone --depth 1 https://github.com/tdimino/claude-code-minoanWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/tdimino/claude-code-minoan/claude-tracker-recent)<a href="https://agentmods.dev/commands/tdimino/claude-code-minoan/claude-tracker-recent"><img src="https://agentmods.dev/badge/commands/tdimino/claude-code-minoan/claude-tracker-recent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/tdimino/claude-code-minoan/claude-tracker-recent"><img src="https://agentmods.dev/badge/commands/tdimino/claude-code-minoan/claude-tracker-recent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00000 | $0.00172 |
| Opus 5.5 | $0.00000 | $0.00069 |
| Sonnet 5.5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
claude-tracker-recent 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 1mo 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.
What it actually says
Recent Claude Sessions (tracker.db)
The fast listing: recent sessions straight from tracker.db, no transcript parsing.
Usage:
/claude-tracker-recent— last 10 sessions/claude-tracker-recent --limit 20 --project knossot/claude-tracker-recent --since 24h --model opus/claude-tracker-recent --json
Arguments
$ARGUMENTS
Instructions
node ~/.claude/skills/claude-tracker-suite/scripts/recent-sessions.js $ARGUMENTS
Shows title, project, model, turns, cost, tags, branch, short ID and the resume command per session. Add --copy to put the first resume command on the clipboard (never done by default).
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.
- 1mo ago First seen · 22 lines · 0 tokens per session scan A 4344e0379700
claude-tracker-recent is a command published in the GitHub repository tdimino/claude-code-minoan (41 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 172 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-09-07.
Other commands, from other repositories
ui-evidence
Discover, configure, and run ui-evidence for before/after UI review in this repo.
spec-forge
Use when generating software specifications — full chain ([Idea]→[Decompose]→[PRD]→SRS→Tech Design→Review) or individual documents.
fec-smell
Diagnose frontend code smells with evidence and candidate refactorings without changing business code.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.