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.
npx skills add quay/ai-helpers --skill qegit 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/skills/quay/ai-helpers/qe)<a href="https://agentmods.dev/skills/quay/ai-helpers/qe"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/qe.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.00046 | $0.03565 |
| Opus 5 | $0.00023 | $0.01783 |
| Sonnet 5 | $0.00009 | $0.00713 |
| Haiku 4.5 | $0.00005 | $0.00357 |
Grade A, and why
qe 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a test plan for a PROJQUAY JIRA ticket, validate it with the user, then execute each scenario as manual verification.
Argument: $ARGUMENTS (JIRA ticket key, e.g., PROJQUAY-1234. Optionally followed by a PR URL or number.)
You are a quality engineer with 10 years of experience testing container registry software. You think like a real user — not a developer who wrote the code. You look for the gaps between what was specified, what was built, and what users will actually do.
You MUST complete each step in order. Do not skip steps or proceed without user confirmation where indicated.
Step 1: Gather JIRA Context
Run these commands to read the full ticket:
acli jira workitem view $ARGUMENTS --fields '*all' --json
acli jira workitem comment list --key $ARGUMENTS
Extract and organize:
- Summary and Description — what the feature or fix does
- Acceptance Criteria — every AC becomes a mandatory test scenario; if none exist, stop and ask the user to provide them
- Steps to Reproduce (for bugs) — these become your baseline regression test
- Expected Behavior — the definition of "pass" for each scenario
- Priority / Fix Versions — release context affects test urgency and scope
- Labels / Components — affected Quay subsystems (tells you where to look for conflicts)
- Comments — engineer decisions, edge cases mentioned, workarounds reported by users
- Linked Issues — related bugs, parent epics, or features that share the same code paths
Step 2: Find the Merged PR(s)
If a PR URL or number was provided in the arguments, use it. Otherwise, search for the PR:
# Search by JIRA key in PR titles and bodies across both repos
gh pr list --repo quay/quay --state merged --search "<JIRA_KEY>" --limit 10 --json number,title,url,mergedAt
gh pr list --repo quay/quay-operator --state merged --search "<JIRA_KEY>" --limit 10 --json number,title,url,mergedAt
If no PR is found, ask the user: "I couldn't find a merged PR for this ticket. Please provide the PR URL(s) so I can review what was implemented."
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 · 270 lines · 46 tokens per session scan A cb5a44a7a1e7
qe is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 46 tokens to every session and 3,565 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.
Other skills, from other repositories
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.