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-implement)<a href="https://agentmods.dev/commands/catwillgh/mainframe/mainframe-tickets-implement"><img src="https://agentmods.dev/badge/commands/catwillgh/mainframe/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/mainframe-tickets-implement"><img src="https://agentmods.dev/badge/commands/catwillgh/mainframe/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.02315 |
| Opus 5.5 | $0.00000 | $0.00926 |
| Sonnet 5.5 | $0.00000 | $0.00463 |
| Haiku 4.5 | $0.00000 | $0.00231 |
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 9d 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 — 96 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.
When the user starts a native goal and then invokes this command separately, process the campaign under that existing goal. Preserve progress through continuations; do not create another goal or stop after the first completed ticket.
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.
Select only docs/tickets/open/ready/ records with execution: autonomous and an evidenced Autonomous implementation boundary. Do not consume user-approved records through this queue-wide command. Keep the active record in ready while implementing. Add Implementation with source locations, pre-change evidence, checks, limitations and checkpoint references; preserve investigation, acceptance, identity and execution metadata. Move a completed verified correction to open/needs-verification/; route missing evidence to open/needs-scope-review/, unresolved user choices to open/needs-decision/, and disproved or duplicate claims to archive/rejected/ with evidence. Save continuation and resulting commit identities under .campaigns/. Preserve ignored record ownership and validate YAML, destination and links after each move.
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.
- 9d ago Changed 8e1b1ca468d7
- 10d ago Changed · +15 lines 7f689b68780d
- 15d ago First seen · 81 lines · 0 tokens per session scan A cef29276a8a6
mainframe-tickets-implement is a command published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,315 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
add-package
Add and configure new project dependencies.
changelog-demo-command
Demo changelog automation features.
opsx-bulk-archive
Archive multiple completed changes at once.
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable, then Phase 6 post-merge close once the PR is verified merged. Not Done until…
estimate
Estimate task effort with confidence levels.
gate-check
Validate readiness to advance between phases.