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 escoffier-labs/skillet --skill ticket-railgit clone --depth 1 https://github.com/escoffier-labs/skilletWrote 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/escoffier-labs/skillet/ticket-rail)<a href="https://agentmods.dev/skills/escoffier-labs/skillet/ticket-rail"><img src="https://agentmods.dev/badge/skills/escoffier-labs/skillet/ticket-rail/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/escoffier-labs/skillet/ticket-rail"><img src="https://agentmods.dev/badge/skills/escoffier-labs/skillet/ticket-rail.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.00071 | $0.01332 |
| Opus 5.5 | $0.00028 | $0.00533 |
| Sonnet 5.5 | $0.00014 | $0.00266 |
| Haiku 4.5 | $0.00007 | $0.00133 |
Grade A, and why
ticket-rail 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ticket-rail
The ticket rail is where orders hang until a cook reads them: is it a real order, is it already on the line, whose station is it. This skill is that read for incoming issue reports. It decides what the report is, whether it duplicates something, and whether anyone may start fixing it, before a single line of code is written.
Core principle: no confirmed repro, no authored fix. A report is a lead; a reproduction is evidence.
Procedure
- Freeze the source coordinates. Record the exact thread, issue URL, permalink, and reporter message you are triaging, and keep them unchanged. Every later read, and any reply the operator has asked for, uses those, never a later comment or a different thread.
- Read the whole report. The root, every reply, every attachment. Capture reporter wording, version, environment, expected versus observed behavior, frequency, trigger, error text, and any link to an existing issue, commit, or PR. Read screenshots, logs, and traces; if an attachment cannot be read, say so rather than guess what it shows. Use evidence already in the thread first. Asking the reporter anything is something the operator must have requested; otherwise put the question in the verdict.
- Trace the cause, bounded. Find the code path from the reported action to the observed result, whether the symptom belongs to that code or a dependency, recent changes if it looks like a regression (lineage), and whether a merged commit or open PR already addresses it. Keep confirmed facts apart from hypotheses. The pass need not find the root cause, only avoid routing to the wrong owner. If the repo cannot be read, say cause tracing was unavailable.
- Classify as one of:
bug,performance(a bug with measurements to preserve),feature,question, orreroute(another project or owner). If bug versus feature is unclear, do not file; ask one focused question. - Dedupe. Search the tracker by exact error text, area, trigger, symptom, version window, and suspected commit. Choose an outcome:
What ships with it
2 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 · 67 lines · 71 tokens per session scan A e7562a692160
ticket-rail is a skill published in the GitHub repository escoffier-labs/skillet (4 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,332 once invoked, about $0.0003 per session on Opus 5.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-10-21.
Other skills, from other repositories
task-forest
Maintains a repo-local task forest or task DAG for the current workspace. Use when the user asks to initialize or update a task forest, close a session, summarize evolving project work, align a request with a global goal, track progress/history/deviations/todos, save or apply a task proposal, or export the…
handoffplan
Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…