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/create-epic-from-feature)<a href="https://agentmods.dev/commands/quay/ai-helpers/create-epic-from-feature"><img src="https://agentmods.dev/badge/commands/quay/ai-helpers/create-epic-from-feature.svg" alt="Measured on agentmods" 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.00015 | $0.03425 |
| Opus 5 | $0.00008 | $0.01713 |
| Sonnet 5 | $0.00003 | $0.00685 |
| Haiku 4.5 | $0.00002 | $0.00343 |
Grade A, and why
create-epic-from-feature 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.
How it starts
The opening of the file, as written. The whole thing — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Epic from Feature
Analyze a JIRA feature and generate a comprehensive epic title and description. This command analyzes the feature in the context of the Quay codebase, displays the generated epic for review, and creates it in JIRA.
Feature Key
The JIRA feature to convert to an epic: $ARGUMENTS
Phase 1: Fetch and Analyze Feature
Step 1: Retrieve Feature Details
Fetch the complete feature information from JIRA:
acli jira workitem view $ARGUMENTS
Extract and analyze:
- Feature summary and description
- Component (ui, api, data, buildman, storage, workers, etc.)
- Current status and priority
- Labels and tags
- Comments and discussion context
- Linked issues (dependencies, related work)
- Acceptance criteria
- Original requester and stakeholders
- Story points or estimates (if present)
IMPORTANT - Customer Data Sanitization:
- Remove all customer-specific information from the epic content
- Replace customer/company names with generic terms like "customer", "organization", "enterprise user"
- Redact specific deployment details, URLs, or infrastructure information
- Use generic use cases instead of customer-specific scenarios
- Remove any support case numbers or customer ticket references
- Focus on the technical problem and solution, not customer identifiers
Step 2: Determine Feature Scope
Analyze whether this feature warrants epic-level promotion:
Questions to consider:
- Does this span multiple components or teams?
- Will this take multiple sprints to complete?
- Are there multiple distinct sub-features or stories needed?
- Does this represent a significant new capability or major refactor?
- Are there multiple stakeholders or cross-team dependencies?
If the feature is too small for an epic:
- Inform the user that this may not need epic-level tracking
- Explain why (e.g., "single component change", "1-2 sprint effort")
- Ask if they still want to proceed
Step 3: Understand Codebase Context
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 · 501 lines · 15 tokens per session scan A 9619d04f1b43
create-epic-from-feature is a command published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 15 tokens to every session and 3,425 once invoked, about $0.0001 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.
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.