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/mainframe-tickets-implementnpx skills add CATWILLgh/MAINFRAME --skill mainframe-tickets-implementgit clone --depth 1 https://github.com/CATWILLgh/MAINFRAMEWrote 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/catwillgh/mainframe/mainframe-tickets-implement)<a href="https://agentmods.dev/skills/catwillgh/mainframe/mainframe-tickets-implement"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/mainframe-tickets-implement.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.00083 | $0.01017 |
| Opus 5 | $0.00042 | $0.00508 |
| Sonnet 5 | $0.00017 | $0.00203 |
| Haiku 4.5 | $0.00008 | $0.00102 |
Grade A, and why
mainframe-tickets-implement 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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement ready tickets
Treat the native Goal objective and any plain-language scope supplied with the
explicit invocation as the run boundary. An empty scope means every ticket in
docs/tickets/open/ready/ carrying execution: autonomous and the complete
evidenced autonomous boundary. Process one ticket at a time until that selected
queue is exhausted, the user pauses or cancels the run, or no eligible work can
continue because of an evidenced external blocker. Never consume
execution: user-approved; only the exact one-ticket Goal produced by
mainframe-init may implement it.
Before changing a ticket, read ticket-format.md. Use the owning engineering skill and its testing boundary when specialized knowledge is needed. Load mainframe-testing-strategy only when the ticket requires a deliberate cross-cutting decision about test levels, suite cost, infrastructure, or broad regression coverage.
Recheck the ticket
Confirm that the ticket remains in open/ready/, its evidence still matches the
current repository, its execution: autonomous eligibility is supported by the
required autonomous boundary, and its stated scope covers the meaningful
affected paths. Do not silently reconstruct missing eligibility or expand a
ticket whose blast radius is materially incomplete.
- Return it to
open/needs-scope-review/when the execution marker, fixed expected behavior, cited authority, exclusions, or affected scope is missing or stale. - Return it to
open/needs-scope-review/when affected locations or consequences require separate refinement. - Move it to
open/needs-decision/when implementation exposes a product, business-logic, material infrastructure, destructive-action, or authority choice owned by the user. - Continue with other eligible tickets after routing one away from
ready.
Establish red evidence
Before changing behavior, obtain the smallest faithful failing test, reproduction, measurement, or other observable proof when it can demonstrate the reported gap. Confirm that it fails for the intended reason, not because of unrelated setup. Do not create a ceremonial test for documentation-only, generated, or purely structural work that a deterministic check proves better.
What ships with it
1 file 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.
- 3d ago First seen · 99 lines · 83 tokens per session scan A 950a76244172
mainframe-tickets-implement is a skill published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 13d ago), licensed MIT. It adds 83 tokens to every session and 1,017 once invoked, about $0.0004 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
cc-hooks
Multi-agent hook system: author hooks once as rulesync-canonical hooks.json (HookDefinitionSchema), deploy via superskill install / superskill hook emit to Claude Code, Codex, OpenCode, Pi (pi-hooks), and Gemini CLI. Covers command, prompt, and http hooks, cross-platform event mapping, and safety invariants.
built-for-shopify-standards
Prepare a Shopify app for Built for Shopify status. Covers current quality criteria, performance, accessibility, Shopify admin integration, compliance webhooks, observability, support, application readiness, and ongoing eligibility.
dev-troubleshooting
Use when a Shopify dev workflow is failing — shopify app dev cryptic errors, Cloudflare tunnel not starting, App Bridge v3→v4 migration 'No AppBridge context provided', GraphQL 200 OK with throttle errors, webhook 401, double-subscribed webhooks, app proxy 404, REST 302 loops, Rust function wasm-validator errors…
merchant-pain-prevention
Use when designing, building, reviewing, or shipping a Shopify app to avoid the patterns that get merchants angry (1-2 star reviews, uninstalls, churn). Covers theme injection / leftover code on uninstall, surprise billing, fake urgency, slow scripts, cancel friction, scope creep, bot-only support, broken on platform…
app-pricing-strategy
Use when designing Shopify app pricing, choosing a pricing model (flat tiered / usage-based / freemium / hybrid), setting trial length (7/14/30 days), structuring 3-4 tier plans, sizing capped usage, raising prices on existing customers, or writing pricing copy for the App Store listing. Triggers: 'shopify app…
ux-modern-app-feel
Use when you want a Shopify embedded app to feel modern, fast, and opinionated like Linear, Notion, Vercel, or Cron — speed-first, keyboard-first, calm UI, opinionated defaults, no-config success path. Covers keyboard shortcuts inside App Bridge, command palette patterns, micro-interactions Polaris allows, density vs…