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/mainframe-tickets-find)<a href="https://agentmods.dev/commands/catwillgh/mainframe/mainframe-tickets-find"><img src="https://agentmods.dev/badge/commands/catwillgh/mainframe/mainframe-tickets-find/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/commands/catwillgh/mainframe/mainframe-tickets-find"><img src="https://agentmods.dev/badge/commands/catwillgh/mainframe/mainframe-tickets-find.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.00000 | $0.01695 |
| Opus 5.5 | $0.00000 | $0.00678 |
| Sonnet 5.5 | $0.00000 | $0.00339 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
mainframe-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 8d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate random project areas and record proven problems
This is a user-invocable command. Execute it only because the current invocation explicitly selected it. It takes no arguments and operates on the current project. When combined with a native goal, continue the campaign under that goal until the stopping criterion below is met or the user stops it. This command alone does not create a goal or background automation.
Repeatedly choose a random project area, investigate it, immediately persist a supported problem or consolidate new evidence into its existing ticket, then choose another area. Do not implement fixes, assign priorities, decide unresolved product behavior, or advance tickets through later lifecycle stages.
Read the initialized ticket contract
Read docs/tickets/AGENTS.md and check its directory, record-format, and lifecycle rules before queue writes. If the root, contract, or required layout is missing or conflicts with effective project rules, report that mainframe-tickets-init must initialize or reconcile it; do not run initialization implicitly, invent another tracker, or migrate unrelated records. Use docs/tickets/ in the current project only. The directory is state: do not add a YAML status field. Preserve string IDs, required frontmatter, meaningful evidence and links. Exclude .campaigns/ and .migration/ from every ticket scan.
Read only relevant matches across the five docs/tickets/open/ queues for deduplication. Create new records in open/observations/ with id, title, component, created, created-from and an Evidence section. New IDs are quoted four-character lowercase hexadecimal strings checked against open and archived IDs; retain existing IDs. Add new facts to matching open records without changing their lifecycle or execution marker. Record trigger/location, actual and expected behavior with sources, consequence, and uncertainty. Keep this campaign's random-point history and duplicate streak under .campaigns/; never count state files, migration snapshots, or terminal records as open duplicates.
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.
- 8d ago Changed 570640387d19
- 9d ago Changed · +4 lines 838f8b14b957
- 14d ago First seen · 61 lines · 0 tokens per session scan A a1428305b3cb
mainframe-tickets-find is a command published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,695 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-10-02.
Other commands, from other repositories
triage
Query open Node bugs, classify by priority and sub-team, suggest assignments, and generate a triage summary.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
project-stage-detect
Detect project phase and recommend actions.
sprint-plan
Generate or update sprint plan.
feedback
Review comments on your display.dev artifacts, then apply them, reply, and resolve the threads after you approve.
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.