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/quay/ai-helpersWrote 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/quay/ai-helpers/quarterly-plan)<a href="https://agentmods.dev/commands/quay/ai-helpers/quarterly-plan"><img src="https://agentmods.dev/badge/commands/quay/ai-helpers/quarterly-plan/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/quay/ai-helpers/quarterly-plan"><img src="https://agentmods.dev/badge/commands/quay/ai-helpers/quarterly-plan.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.00013 | $0.03066 |
| Opus 5 | $0.00006 | $0.01533 |
| Sonnet 5 | $0.00003 | $0.00613 |
| Haiku 4.5 | $0.00001 | $0.00307 |
Grade A, and why
quarterly-plan scanned grade A with 1 finding 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( How it starts
The opening of the file, as written. The whole thing — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quarterly Planning
Tag JIRA issues with the next quarter's label based on priority triage. Automatically tags Blockers and Criticals, presents Majors for review.
Arguments
Input: $ARGUMENTS
Format: <quarter> [must-have-issues] or add <quarter> <issue-keys>
<quarter>(required): The quarter being planned, e.g.,2026-Q3[must-have-issues](optional): Comma-separated issue keys to always include, e.g.,QUAYIO-1234,QUAYIO-5678
Modes:
- Plan mode (default): Full quarterly planning with priority triage
- Add mode: Quickly add issues to an existing quarter plan
Examples:
/quarterly-plan 2026-Q3
/quarterly-plan 2026-Q3 QUAYIO-1234,QUAYIO-5678
/quarterly-plan add 2026-Q3 QUAYIO-1900,QUAYIO-1905
Phase 0: Prerequisites
Step 1: Check acli Installation
which acli
If acli is NOT installed, display setup instructions and stop.
Step 2: Check Authentication
acli jira auth status
If not authenticated, attempt login using token from ~/.config/acli/token.txt, ~/.acli-token, or $JIRA_API_TOKEN. Read email from ~/.config/acli/jira_config.yaml.
Step 3: Store User Email
cat ~/.config/acli/jira_config.yaml
Extract the email field for use throughout the skill.
Phase 1: Parse Arguments and Determine Scope
Step 1: Parse Quarter
Parse $ARGUMENTS to extract:
- Target quarter: The quarter being planned (e.g.,
2026-Q3) - Must-have issues: Optional comma-separated issue keys
Derive the previous quarter automatically:
- Q2 -> previous is Q1 (same year)
- Q3 -> previous is Q2 (same year)
- Q4 -> previous is Q3 (same year)
- Q1 -> previous is Q4 (previous year)
Step 2: Derive Label Names
Labels follow the format quay-{YYYY}-Q{N} (capital Q):
- Current quarter label: e.g.,
quay-2026-Q2 - Target quarter label: e.g.,
quay-2026-Q3
Step 3: Determine Project
Ask the user which project to plan for:
Which project?
- QUAYIO (default)
- PROJQUAY
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.
- 4d ago First seen · 413 lines · 13 tokens per session scan A 8a6b8df8419f
quarterly-plan is a command published in the GitHub repository quay/ai-helpers (3 stars, last pushed 21d ago), licensed MIT. It adds 13 tokens to every session and 3,066 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.