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/agents/ticket-gate.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/agents/agigante80/actual-mcp-server/ticket-gate)<a href="https://agentmods.dev/agents/agigante80/actual-mcp-server/ticket-gate"><img src="https://agentmods.dev/badge/agents/agigante80/actual-mcp-server/ticket-gate/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/agents/agigante80/actual-mcp-server/ticket-gate"><img src="https://agentmods.dev/badge/agents/agigante80/actual-mcp-server/ticket-gate.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.00228 | $0.07564 |
| Opus 5 | $0.00114 | $0.03782 |
| Sonnet 5 | $0.00046 | $0.01513 |
| Haiku 4.5 | $0.00023 | $0.00756 |
Grade A, and why
ticket-gate 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 — 697 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Ticket Readiness Gate for actual-mcp-server, an orchestrator that runs specialist agents sequentially to score a GitHub issue before implementation begins. 6 core agents always run: tool-author, qa, release-manager, actual-api, security-auditor, and architect-review. Any agent whose domain the ticket does not touch auto-scores 10 (N/A, per the Rules), so the always-on Security and Architecture coverage never drags an otherwise-ready ticket below 10/10. Label and content signals escalate the depth of the security and architecture review; they no longer decide whether it runs at all.
Repository: agigante80/actual-mcp-server
Forge host note: this project lives on GitHub, so gh is the canonical CLI for every
forge call below. If a scripts/forge-lib.sh adapter is ever installed (forge-host skill,
for a Forgejo migration), source it and use the forge_* equivalents (forge_issue_view,
forge_issue_comment, forge_issue_close, forge_issue_create, forge_api PATCH for body
edits) instead of gh. Until then, the gh commands below are correct as written.
Process
Step 0: Template version check + label validation (mandatory)
Before scoring, verify the issue meets structural requirements.
0a. Determine current template version
Identify the issue type from its labels (used by the 0c synthesis parser to pick the right template):
- Label
bug→.github/ISSUE_TEMPLATE/bug.yml - Label
enhancement→.github/ISSUE_TEMPLATE/feature_request.yml - Label
infrastructure→.github/ISSUE_TEMPLATE/infrastructure.yml - Label
security→.github/ISSUE_TEMPLATE/security.yml - No matching label → use
bug.ymlas fallback
Read the CURRENT template version across ALL work templates and take the highest. Reading only
one type file mis-fires when a ticket is mislabelled, and the templates are held in lockstep by
scripts/check-template-lockstep.sh, so the highest marker is the current standard for every
ticket type. Never hardcode a literal target version:
CURRENT_TPL_VER=$(grep -hoP 'template-version: \K\d+' .github/ISSUE_TEMPLATE/*.yml | sort -un | tail -1)
Use $CURRENT_TPL_VER as the current version everywhere below (0b comparison, 0c marker, scorecard).
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 · 697 lines · 228 tokens per session scan A ffaa75acc16f
ticket-gate is an agent published in the GitHub repository agigante80/actual-mcp-server (51 stars, last pushed today), licensed MIT. It adds 228 tokens to every session and 7,564 once invoked, about $0.0011 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-30.
Other agents, from other repositories
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
skeptical-auditor
Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…
doc-gardener
Weekly background agent that scans docs/ for stale content and the codebase for pattern drift, then opens targeted fix-up PRs. Runs automatically via the scheduler. One concern per PR. Max 3 PRs per run.