Borrowing it
Nothing to install: this file belongs to agigante80/actual-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agigante80/actual-mcp-server/main/.claude/commands/gate-ticket.mdgit clone --depth 1 https://github.com/agigante80/actual-mcp-serverWrote 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/agigante80/actual-mcp-server/gate-ticket)<a href="https://agentmods.dev/commands/agigante80/actual-mcp-server/gate-ticket"><img src="https://agentmods.dev/badge/commands/agigante80/actual-mcp-server/gate-ticket/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/agigante80/actual-mcp-server/gate-ticket"><img src="https://agentmods.dev/badge/commands/agigante80/actual-mcp-server/gate-ticket.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.00323 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
gate-ticket 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.
What it actually says
Run the ticket readiness gate on a GitHub issue. (The forge-kit v3 template supports forge detection via the forge-host adapter; this project is GitHub-hosted, so the ticket-gate agent targets agigante80/actual-mcp-server directly.)
Usage
Accepted argument: <issue-number> (required)
Example: /gate-ticket 42
Steps
Use the Agent tool with subagent_type: ticket-gate, passing the issue number as the prompt.
The ticket-gate agent handles all steps:
- Template version check: auto-synthesises missing sections if the template version is below v4 or missing (no BLOCK)
- Label validation: requires at least one area label (
backend,infrastructure,security,actual-api,documentation) - Fetches the issue from agigante80/actual-mcp-server
- Reads project context (CLAUDE.md, actual-adapter.ts, toolFactory.ts, schemas/common.ts)
- Runs the 6 core agents (tool-author, qa, release-manager, actual-api, security-auditor, architect-review); any whose domain the ticket does not touch auto-score 10 (N/A)
- Adds any content-triggered specialists selected by labels and content, and runs all agents sequentially
- Compiles and posts the scorecard as a GitHub comment
- Returns PASS or BLOCKED with specific required changes
All agents must score 10/10 for the ticket to be considered implementation-ready.
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 First seen · 26 lines · 0 tokens per session scan A 64f0c298c924
gate-ticket is a command published in the GitHub repository agigante80/actual-mcp-server (51 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 323 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-08-30.
Other commands, from other repositories
commands
A set of project-management commands for maintaining collaboration rules, documentation, plans, thoughts, and project configuration. It covers tasks such as adding commands, updating governance instructions, recording ideas, and organizing roadmap items.
issue-prd-generation
You are generating a comprehensive Product Requirements Document (PRD) for a GitHub issue. This PRD will be passed to a separate AI agent instance with ONLY THIS CONTEXT for implementation. Write with that constraint in mind.
artifact-insight-scan
Analyze the provided project artifacts for missed insights, action items, and follow-ups that should become tracked issues.
polish-repo-community
Phase 3 of polish-repo: Community infrastructure, issue templates, roadmap, contributor experience, and signs of life.
estimate-point
Phases 4-5 of estimating-tickets. Multi-agent consensus pointing per ticket + AI productivity multiplier.
estimate-scope
Phase 1-3 of estimating-tickets. Ingest the test card, validate external-domain constraints, build a structural repo map, decompose into tickets tagged by repo.