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-implement)<a href="https://agentmods.dev/commands/catwillgh/mainframe/tickets-implement"><img src="https://agentmods.dev/badge/commands/catwillgh/mainframe/tickets-implement/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/tickets-implement"><img src="https://agentmods.dev/badge/commands/catwillgh/mainframe/tickets-implement.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.01397 |
| Opus 5 | $0.00000 | $0.00698 |
| Sonnet 5 | $0.00000 | $0.00279 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
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 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement project tickets
This is a user-invocable command. Execute it only because the current invocation explicitly selected it. It takes no arguments: every invocation processes the complete current project queue that is ready for implementation.
Implement each eligible ticket completely within its evidenced boundary, validate the result locally, route it for independent verification, and continue until no ready ticket remains that this command can safely process. Do not discover or refine unrelated problems, verify your own implementation as independent work, deploy, or close tickets during this command.
Establish the queue and authority
Resolve the current project root, its configured issue route, and the lifecycle states that represent ready work and implemented work awaiting independent verification. Do not use another project's queue or MAINFRAME's central harness-feedback queue.
If the project has no configured issue route or implementation lifecycle, return the exact missing configuration and stop without inventing one. If the queue is external, mutate it only when the current caller supplied that authority. Otherwise return the exact missing write action instead of claiming a completed transition.
The explicit invocation authorizes the local, reversible project and ticket changes required to implement ready tickets in the current checkout. It does not authorize deployment, writes to remote or shared environments, destructive data operations, material infrastructure changes, repository-history changes, commits, or pushes. Preserve the starting branch, unrelated dirty work, existing processes, and user-owned configuration.
Process exactly one ticket at a time
Read the ready queue afresh. Select one ticket and keep it as the only active ticket until it has been implemented and routed or found ineligible and rerouted. Do not work on separate tickets concurrently. Delegated work, when available and useful, must remain bounded to the same active ticket and return its changes, evidence, limitations, and unverified assumptions for inspection.
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 · 75 lines · 0 tokens per session scan A 55c514ec3674
tickets-implement 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,397 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
epic-validate
Validate epic readiness, dependencies, and coordination policy.
aqa-flow
Router workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
autoresearch
Autonomous improvement loop — scan codebase metrics, scaffold experiment files, run agent-driven iterations until metric improves.
plan-eng-review
Engineering architecture gate — lock architecture, diagrams, edge cases, and test matrix before writing implementation code.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.