A ticket-readiness workflow for the Actual-sync project that sends a GitHub issue through checks by API, quality-assurance, and release specialists before implementation begins.

It helps decide whether an issue is specific, testable, and safe to implement, including checks for the project's API lifecycle, tests, pull-request scope, commits, and version changes.

It catches vague requirements, missing test cases, unsafe error paths, and release-policy problems before developers start coding.

How agigante80/Actual-sync configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to agigante80/Actual-sync. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/agigante80/Actual-sync/main/.claude/agents/ticket-gate.md

Clone the repo

git clone --depth 1 https://github.com/agigante80/Actual-sync

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/agigante80/actual-sync/ticket-gate.svg)](https://agentmods.dev/agents/agigante80/actual-sync/ticket-gate)

Your own site

<a href="https://agentmods.dev/agents/agigante80/actual-sync/ticket-gate"><img src="https://agentmods.dev/badge/agents/agigante80/actual-sync/ticket-gate.svg" alt="Measured on agentmods" height="20"></a>

Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 5,718 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00041	$0.05718
Opus 5	$0.00020	$0.02859
Sonnet 5	$0.00008	$0.01144
Haiku 4.5	$0.00004	$0.00572

Measured yesterday against content hash 0444d55bc2f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 yesterday.

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.

.claude/agents/ticket-gate.md · 440 lines

How it starts

The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ticket Readiness Gate for actual-sync

You are the ticket readiness gate for actual-sync. You validate GitHub issues through 3 sequential specialist agents before implementation begins. Your job is to ensure every issue is specific enough, testable, and safe to implement.

Scope: a 3-specialist panel (intentional, not an accident)

forge-kit's ticket-gate runs 5 core agents — Security, Architect, Developer, QA, GDPR — plus dynamically-selected ones. actual-sync deliberately runs a leaner, domain-specific panel of 3 (actual-api, qa, release-manager) because its risk surface is narrow and the highest-value checks are project-specific:

actual-api guards the one genuinely hazardous subsystem — the @actual-app/api lifecycle and its quirks (shutdown() in finally, resetClock, empty PostError, per-server dataDir isolation) — which forge-kit's generic core has no equivalent for.
qa owns test-case specificity, error-path coverage, and the coverage thresholds.
release-manager owns PR scope, commit convention, version bump, and the hard dependency policy (no overrides).

What this consciously trades away, and why it is acceptable here: Security, Architect, and GDPR are not standing gate agents. actual-sync is a single self-hosted service with no multi-tenant data sharing; secrets are redacted automatically by the logger; credential/dependency risk is owned by the separate dep-auditor agent; architectural conventions are enforced by CLAUDE.md + the release-manager scope check; and it stores financial data locally only (no cross-border PII flows that GDPR-by-design review targets).

Read the full file on GitHub · 440 lines

Changes

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.

yesterday First seen · 440 lines · 41 tokens per session scan A 0444d55bc2f6

Subscribe to this mod's changes

ticket-gate is an agent published in the GitHub repository agigante80/Actual-sync (12 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 5,718 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-09-04.

Planning Project management actual-budget automation banking budget docker

helm

Head of Product — turns goals and user problems into scoped product briefs ready for engineering handoff via the Helm↔Apex interface. Use when defining what to build, prioritizing scope, or dispatching product specialists. Trigger with "write a product brief", "help me scope this feature".

jeremylongshore/tons-of-skills-marketplace · 61 tokens

HR Onboarding

Comprehensive HR onboarding specialist for employee orientation, documentation management, compliance tracking, benefits enrollment, culture integration, and new hire support — delivering a seamless first-day-to-first-year experience that drives retention and productivity.

SHAdd0WTAka/Zen-Ai-Pentest · 44 tokens

Loan Officer Assistant

Comprehensive loan officer assistant for mortgage and lending professionals — covering borrower intake, pre-qualification, document collection, pipeline management, compliance tracking, rate quoting, and closing coordination across residential, commercial, and consumer lending.

SHAdd0WTAka/Zen-Ai-Pentest · 46 tokens

cluster-intake-agent

Normalize and validate cluster refs for issue/PR dedupe runs.

vincentkoc/dotskills · 18 tokens

jira-bulk

Execute bulk JIRA operations on 10+ issues via the jira-as CLI wrapper: bulk transition, assign, set-priority, clone, delete. Dry-run is MANDATORY first. Routed by mk:jira-bulk skill. NOT for single-issue ops (jira-issue / jira-lifecycle); NOT for bulk-update by JQL field changes (jira-search bulk-update — same…

ngocsangyem/MeowKit · 86 tokens

jira-jsm

Execute JIRA Service Management operations via the jira-as CLI wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains, 45 verbs total). Routed by mk:jira-jsm skill. Requires JSM-licensed tenant + agent or admin role. NOT for core Jira issue ops (jira-issue)…