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-implementnpx skills add CATWILLgh/MAINFRAME --skill tickets-implementgit clone --depth 1 https://github.com/CATWILLgh/MAINFRAMEWhat 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.00035 | $0.00631 |
| Opus 5 | $0.00017 | $0.00316 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
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 2d 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
Implement ready tickets
Do not start implementation in the invocation turn. Return only this copyable block, with the invocation argument preserved as written:
/goal Follow the loaded tickets-implement workflow. Scope: "$ARGUMENTS"; an empty scope means every ticket in open/ready explicitly marked execution: autonomous with a complete evidenced autonomous boundary. Continue one ticket at a time until each eligible ticket has either a complete locally validated implementation in open/needs-verification or has been returned to needs-scope-review or needs-decision with the newly discovered boundary; or stop when the user asks to pause or cancel, or with an evidenced external blocker that prevents any eligible work from continuing. Never consume execution: user-approved in this queue-wide run. Before finishing, surface ticket outcomes, red and green evidence, validation, commits, 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/ready tickets carrying execution: autonomous and the
complete autonomous boundary required by ticket-format.md. A plain-language
argument may narrow the queue by ticket id, path, component, or concern but
grants no new authority. Skip execution: user-approved; only the exact goal
produced by init ticket <id> may implement it. For each autonomous ticket:
- Recheck that its eligibility evidence, fixed expected behavior, and scope
still match the current repository. Missing or stale eligibility returns the
ticket to
needs-scope-review; do not reconstruct or assume it here. - Obtain a focused red test, reproduction, measurement, or other observable proof before changing behavior when it can demonstrate the gap. Do not add a ceremonial test for a purely structural change.
- Implement the complete smallest solution, including necessary regression coverage and cleanup. Do not leave TODOs, placeholders, suppressions, or a partial shopping list in code.
- Run focused checks first, then the proportionate broader validation needed
for the affected business and technical contracts. Append concise evidence
and changed locations to the ticket and move it to
needs-verification. - Create a local Conventional Commit for a coherent verified unit during a long run, without staging unrelated work.
If implementation exposes missing blast radius, return the ticket to
needs-scope-review. If it exposes a real user-owned choice, move it to
needs-decision and continue with other eligible tickets. Record unrelated
problems as observations. Do not independently close work implemented earlier
in this same session; closure belongs to a fresh verification run.
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.
- 2d ago First seen · 47 lines · 35 tokens per session scan A 4f2f976402fd
tickets-implement is a skill published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 11d ago), licensed MIT. It adds 35 tokens to every session and 631 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
discord-webhook
Send trading alerts, signals, and analysis summaries to Discord via webhook. Integrates with realtime-alert-pipeline, trading-brain, and trade-journal-analytics.
agentforge-protocol
Use when doing non-trivial coding with Hermes, OpenClaw, Claude Code, Codex CLI, or similar autonomous coding agents. Orchestrates Karpathy-style minimal-change discipline, grill-plan intake, TDD, systematic debugging, subagent-driven implementation, spikes, and pre-commit review into one end-to-end workflow.
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.