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 summarygit 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/summary)<a href="https://agentmods.dev/skills/quay/ai-helpers/summary"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/summary/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/skills/quay/ai-helpers/summary"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/summary.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.00029 | $0.00648 |
| Opus 5.5 | $0.00012 | $0.00259 |
| Sonnet 5.5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
summary 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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Summary
This skill can be invoked at any point. It summarizes whatever exists so far.
Your Role
Scan the artifact directory, read what's there, and synthesize the important findings into a single summary. Surface things that might otherwise get buried: related PRs, reproduction failures, review concerns, unconfirmed assumptions.
Process
Step 1: Discover Artifacts
find artifacts/quay-bugfix/ -type f -name '*.md' ! -name 'summary.md' 2>/dev/null | sort
If artifacts/quay-bugfix/ doesn't exist or is empty, report that no
artifacts have been generated yet and stop.
Step 2: Read All Artifacts
Read every artifact found. Don't skip any.
Step 3: Extract Key Findings
Pull out information in these categories:
- Existing work discovered: Related PRs, duplicate issues, prior attempts
- Bug understanding: What the bug is, whether it was reproduced
- Root cause and fix: Identified cause, what was changed and why
- Testing status: Full suite results, new regression tests
- Review concerns: Verdict, specific concerns, outstanding items
- PR status: URL, branch target, CI status
- Backport: Required or not
Step 4: Present Summary
## Quay Bugfix Workflow Summary
**Ticket:** [JIRA key and title]
**Status:** [where the workflow stopped]
### Key Findings
- [3-5 bullet points max]
### Decisions Made
- [choices made during the workflow]
### Outstanding Concerns
- [review caveats, untested edge cases — or "None"]
### Artifacts
- [list with one-line descriptions]
### PR
- [URL and status, or "Not yet created"]
### Backport
- [Required/Not required, and status]
Keep it tight — if it's as long as the artifacts, it's not a summary.
Step 5: Write Summary Artifact
Save to artifacts/quay-bugfix/summary.md.
Rules
- Read, don't assume. Base everything on what artifacts actually say.
- Flag what's missing. If a phase was skipped, say so.
- Don't editorialize. Report what artifacts say without softening.
- Keep it short. Under 40 lines of Markdown.
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.
- 1mo ago First seen · 101 lines · 29 tokens per session scan A 30b6c24cb0e5
summary is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 29 tokens to every session and 648 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…