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/catwillgh/mainframe/ticketnpx skills add CATWILLgh/MAINFRAME --skill ticketgit clone --depth 1 https://github.com/CATWILLgh/MAINFRAMEWhat 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.00062 | $0.00307 |
| Opus 5 | $0.00031 | $0.00153 |
| Sonnet 5 | $0.00012 | $0.00061 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
ticket 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.
What it actually says
Ticket
Preserve a concrete problem outside the active task's assigned result or agreed definition of done without silently expanding scope. This skill owns ticket intake and, only for an explicitly assigned investigation, initial confirmation that the problem exists. Later profile runs own scope review, implementation, and independent closure verification.
First identify how the problem reached you:
- If it appeared incidentally while completing another task, or a broad discovery run found it as a plausible candidate, read record-observation.md. Do not investigate beyond the evidence needed to describe the observation.
- If the immediate caller explicitly assigned confirmation or focused investigation of the problem, read record-confirmed-problem.md. Confirm it before writing it.
Both paths must read ticket-format.md before creating, moving, renaming, or updating a ticket.
If the problem prevents achieving or verifying the assigned result or agreed definition of done, it is not out of scope. Handle it through the active workflow instead of using this skill.
What ships with it
3 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.
- 2d ago First seen · 32 lines · 62 tokens per session scan A 463086e66cde
ticket is a skill published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 11d ago), licensed MIT. It adds 62 tokens to every session and 307 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
file-organizer
Triggered when the user needs to organize project files, analyze directory structure, or generate a project report. Use MCP tools to read file contents and produce a structured organization report. Trigger phrases include "help me organize this project", "look at the directory structure", "generate a project summary".
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.
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…
af
Agent Farm CLI quick reference. Use when running af commands to check correct syntax, subcommands, and flags. Prevents guessing at command names.
audit
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to "audit the project", "run a full audit", "project health check", "audit my code", "codebase audit", or "comprehensive review".