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/an8079/take-skillsWrote 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/an8079/take-skills/takes-ultraqa)<a href="https://agentmods.dev/commands/an8079/take-skills/takes-ultraqa"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-ultraqa/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/an8079/take-skills/takes-ultraqa"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-ultraqa.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.00023 | $0.00757 |
| Opus 5 | $0.00012 | $0.00378 |
| Sonnet 5 | $0.00005 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
ultraqa 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 9d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ultraqa - UltraQA 质量循环模式
测试-验证-修复循环，直到质量目标达成。
使用方式
/ultraqa "目标"
或
ULTRAQA
质量循环
测试循环
工作流程
┌──────────────────────────────────────────────────────┐
│ UltraQA Loop │
├──────────────────────────────────────────────────────┤
│ │
│ ┌───────────┐ │
│ │ Test │ 执行测试 │
│ └─────┬─────┘ │
│ │ │
│ ▼ │
│ ┌───────────┐ │
│ │ Verify │ 验证测试结果 │
│ └─────┬─────┘ │
│ │ │
│ 通过？├──────────────┐ │
│ ┌────┴────┐ │ │
│ │ │ 否 │
│ │ 是 │ │
│ │ │ │ │
│ ▼ │ ▼ │
│ ┌──────┐ │ ┌───────────┐ │
│ │ Done │ │ │ Fix │ │
│ └──────┘ │ └─────┬─────┘ │
│ │ │ │
│ └──────────┴───────────────────────────┘
│ │
└──────────────────────────────────────────────────────┘
适用场景
| 场景 | 说明 |
|---|---|
| 构建验证 | 确保 CI/CD 构建通过 |
| 测试通过 | 确保所有测试通过 |
| Lint 检查 | 确保代码风格一致 |
| 类型检查 | 确保 TypeScript 类型正确 |
| 安全扫描 | 确保无安全漏洞 |
质量标准
| 标准 | 说明 |
|---|---|
| 测试覆盖率 | ≥ 80% |
| 所有测试通过 | 0 failed |
| Lint 通过 | 0 warnings |
| 类型检查通过 | 0 errors |
特点
| 特点 | 说明 |
|---|---|
| 目标驱动 | 明确的质量目标 |
| 自动修复 | 测试失败时自动尝试修复 |
| 持续验证 | 直到所有检查通过 |
| 详细报告 | 每次迭代的详细结果 |
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.
- 9d ago First seen · 95 lines · 23 tokens per session scan A 648a723f1f84
ultraqa is a command published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 757 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-08-31.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.