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 agentmods add skills/aaddrick/ticketmill/mill-reviewnpx skills add aaddrick/ticketmill --skill mill-reviewgit clone --depth 1 https://github.com/aaddrick/ticketmillWrote 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/aaddrick/ticketmill/mill-review)<a href="https://agentmods.dev/skills/aaddrick/ticketmill/mill-review"><img src="https://agentmods.dev/badge/skills/aaddrick/ticketmill/mill-review.svg" alt="Measured on agentmods" 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 | $0.00060 | $0.04186 |
| Opus 5 | $0.00030 | $0.02093 |
| Sonnet 5 | $0.00012 | $0.00837 |
| Haiku 4.5 | $0.00006 | $0.00419 |
Grade C, and why
mill-review scanned grade C 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- FLAG FOR BATCH REVIEWER: issue #94's body says the local dashboard is a "committed logs/ticketmill/dashboard.md fallback." Step 7c below deliberately ships it as a LOCAL, GITIGNORED, NEVER-COMMITTED file instead. Th How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mill-review: cross-run trend dashboard for ticketmill's own process ledger
Ticketmill journals every batch run it executes against itself and against target repos into a local, gitignored ledger. This skill reads that ledger, never writes to it, and turns it into three views of one data model: things said out loud in the conversation, a shareable HTML Artifact, and a local markdown fallback for sessions without Artifact support.
This skill is read-only against the ledger and touches no engine-owned path. Its only write is the local dashboard file in Step 7c.
Step 1: Resolve the ledger root (never hard-code it)
ROOT = $(git rev-parse --show-toplevel). If that command fails (not a git repo, detached context), fall back toROOT = $(pwd).- Look for
<ROOT>/.claude/ticketmill.json. If it exists and parses, readlogs_dirfrom it. If the file is missing, unparsable, orlogs_diris absent, defaultlogs_dirtologs/ticketmill, the profile schema's own documented default. LOGS = <ROOT>/<logs_dir>.
Never substitute a literal absolute path for LOGS in any step below, even
as a shortcut. This same skill runs against ticketmill's own ledger and
against any onboarded target repo's ledger, and the two roots differ.
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 · 293 lines · 60 tokens per session scan C 23453e539b55
mill-review is a skill published in the GitHub repository aaddrick/ticketmill (15 stars, last pushed 25d ago), licensed MIT. It adds 60 tokens to every session and 4,186 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…