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/tickets-verifynpx skills add CATWILLgh/MAINFRAME --skill tickets-verifygit 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/tickets-verify)<a href="https://agentmods.dev/skills/catwillgh/mainframe/tickets-verify"><img src="https://agentmods.dev/badge/skills/catwillgh/mainframe/tickets-verify.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.00031 | $0.00521 |
| Opus 5 | $0.00015 | $0.00260 |
| Sonnet 5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
tickets-verify 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.
What it actually says
Verify implemented tickets
Use this command from a fresh session that did not implement the queued work. Do not start verification in the invocation turn. Return only this copyable block, with the invocation argument preserved as written:
/goal Follow the loaded tickets-verify workflow. Scope: "$ARGUMENTS"; an empty scope means every eligible ticket in open/needs-verification. Continue one ticket at a time until each eligible implementation has been independently checked and its ticket has either moved unchanged in identity to archive/resolved or returned to ready, needs-scope-review, or needs-decision with precise failed-verification evidence; or stop when the user asks to pause or cancel, or with an evidenced external blocker that prevents any eligible work from continuing. Before finishing, surface ticket verdicts, reproduced evidence, queue transitions, and completion evidence in the conversation.
When that goal starts, first read
ticket-autonomous-runs.md,
ticket-format.md, and the testing-strategy skill.
Work only from open/needs-verification. A plain-language argument may narrow
the queue by ticket id, path, component, or concern but grants no new authority.
Do not verify an implementation produced earlier in the same session.
For each ticket, distrust both its prose and a green command in isolation. Inspect the actual implementation and relevant history, reproduce the original gap or its regression protection, run focused and proportionate broader checks, and verify the affected business contract, error paths, and cleanup behavior. Use deterministic interleavings for concurrency claims and the real consumer or artifact shape when generated output is part of the result.
On success, append concise independent evidence and move the ticket to the
immutable archive/resolved path. On failure, do not repair code inline:
append exact evidence and return the same ticket to ready with its existing
execution route for an incomplete or incorrect implementation,
needs-scope-review for missed scope, or
needs-decision for a newly exposed user-owned choice. A disproved or duplicate
claim goes to archive/rejected. Commit only the resulting ticket-state update
as a coherent local recovery point when appropriate; never modify an archived
file afterward.
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 · 42 lines · 31 tokens per session scan A 95ed8c5557b3
tickets-verify is a skill published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 13d ago), licensed MIT. It adds 31 tokens to every session and 521 once invoked, about $0.0002 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…