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.
git 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/commands/catwillgh/mainframe/tickets-find)<a href="https://agentmods.dev/commands/catwillgh/mainframe/tickets-find"><img src="https://agentmods.dev/badge/commands/catwillgh/mainframe/tickets-find.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.1 | $0.00000 | $0.01082 |
| Opus 5 | $0.00000 | $0.00541 |
| Sonnet 5 | $0.00000 | $0.00216 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
tickets-find 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 today.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find project ticket candidates
This is a user-invocable command. Execute it only because the current invocation explicitly selected it. It takes no arguments: every invocation covers the complete current project.
Start discovery from the current project state every time. Find concrete problem candidates across the complete project, reconcile them with the receiving project's configured open issue queue, and return an evidence-based coverage report. Earlier runs, remembered coverage, and existing tickets are leads and deduplication inputs, never substitutes for a fresh pass. Do not implement, fully refine, prioritize, decide, or close tickets during this command.
Establish the boundary
Resolve the current project root and its configured issue route from the effective project harness. Do not use another repository's queue or MAINFRAME's central harness-feedback queue. If the project has no configured issue route, return the exact missing configuration and ticket-ready findings; do not invent a tracker or initialize a queue as a side effect of discovery.
The invocation authorizes read-only discovery and project-ticket writes only to the extent supplied by the current caller. It does not authorize product changes, external environment mutations, repository-history operations, or broader access. If the configured queue is external and the invocation does not carry write authority for it, keep discovery read-only and return ticket-ready records.
Preserve the current checkout, branch, unrelated dirty work, and existing processes. Do not switch or create branches or worktrees, alter history, stash, clean, commit, push, deploy, or modify application behavior.
Refresh relevant open records
Inspect every open project ticket before searching for new candidates. Recheck its locations, triggering conditions, and claimed mechanisms against the current project tree.
Follow renamed or moved code into current callers and consumers; a missing historical path alone does not prove that a problem disappeared. Add a concise relevance note only when current evidence materially changes an open record. Preserve its identity, evidence history, and lifecycle state. Do not close, reject, split, merge, refine, or reroute tickets in this command.
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.
- today First seen · 61 lines · 0 tokens per session scan A a1428305b3cb
tickets-find is a command published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,082 tokens. 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-09-08.
Other commands, from other repositories
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
team
Virtual eng team orchestrator. Runs a goal end-to-end through the whole team — strategy → plan → build → QA → ship — conducted by the engineering-manager, delegating to every specialist. One entry point that connects /ceo-review, /eng-review, /qa, and /ship.
content-start
Content production session start command. Gives the daily content session a structured start, shows pending work, and sets priorities.
onboard
Project onboarding command. For adapting to a new project quickly and thoroughly.
proposal
Client proposal command. Builds a professional client proposal from project summaries. Valid for 30 days.