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.
npx skills add tdimino/claude-code-minoan --skill codex-tracker-suitegit 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/skills/tdimino/claude-code-minoan/codex-tracker-suite)<a href="https://agentmods.dev/skills/tdimino/claude-code-minoan/codex-tracker-suite"><img src="https://agentmods.dev/badge/skills/tdimino/claude-code-minoan/codex-tracker-suite/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/skills/tdimino/claude-code-minoan/codex-tracker-suite"><img src="https://agentmods.dev/badge/skills/tdimino/claude-code-minoan/codex-tracker-suite.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.00089 | $0.00549 |
| Opus 5 | $0.00044 | $0.00275 |
| Sonnet 5 | $0.00018 | $0.00110 |
| Haiku 4.5 | $0.00009 | $0.00055 |
Grade B, and why
codex-tracker-suite scanned grade B with 1 finding 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 4d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
Run any command with `--help` for filters and JSON output. Add `--include-non-interactive` for `codex exec` and App Server sessions, or `--all-sources` for subagents too. Ordinary searches default to interactive CLI and How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Tracker Suite
Use the bundled wrapper instead of reading Codex's private SQLite databases or rollout files. It talks to the version-matched codex app-server protocol and leaves Codex as the source of truth.
codex-tracker search "topic"
Route the request
- Find a session by topic or transcript text:
search QUERY - Locate every visible match inside one session:
occurrences SESSION_ID QUERY - Browse recent work:
recent - Inspect metadata or the visible conversation:
show SESSION_ID - See sessions loaded in a shared managed runtime:
alive - Produce a shell-safe command for continuing work:
resume SESSION_ID
Run any command with --help for filters and JSON output. Add --include-non-interactive for codex exec and App Server sessions, or --all-sources for subagents too. Ordinary searches default to interactive CLI and IDE sessions, matching Codex's native behavior.
Operating rules
- Keep lookup operations read-only.
resumeprints a command; it does not launch an interactive process. - Return the matching session ID, title, working directory, snippet, and resume command when available.
- Prefer
--jsonwhen another program or agent will consume the result. - Native transcript search is experimental and may take a minute or two on a large history. The wrapper prints progress while waiting and uses a configurable timeout.
- If native full-text search is unavailable, report the compatibility error and suggest
codex resume --all; do not silently scrape private databases. - App Server may update its own state metadata during a read. In a restricted Codex sandbox, request approval for the wrapper command instead of bypassing the sandbox.
- Do not archive, delete, rename, or otherwise mutate sessions unless the user separately asks for that operation. This wrapper intentionally exposes no destructive commands.
- Treat
aliveas a managed-daemon view. Without the shared App Server daemon, use Codex's own session UI or process-level diagnostics instead.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 37 lines · 89 tokens per session scan B 76559225d214
codex-tracker-suite is a skill published in the GitHub repository tdimino/claude-code-minoan (41 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 549 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other skills, from other repositories
weekly-retro
A structured weekly retrospective for a one-person business run with AI agents. It gathers evidence from code, project tools, and canonical business files, then records findings and outcomes.
idea
Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub Project view filtered by label:idea. NOT…
meeting-copilot
Use when preparing for, running, or closing a live meeting with an AI assistant dashboard. Triggers on "meeting copilot", "live copilot", "prepare for a call", "update copilot", "close the session", or requests to turn transcript chunks into meeting questions, topic maps, decisions, and follow-ups.
daily
A daily-planning workflow that reports the current department’s active work and refreshes its weekly plan. It uses the department’s defined task source and follows the project’s local instructions.
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…
copilotkit-channels
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…