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 agentmods add skills/timothyhan/qa-buddy-skills/setupnpx skills add TimothyHan/qa-buddy-skills --skill setupgit clone --depth 1 https://github.com/TimothyHan/qa-buddy-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/skills/timothyhan/qa-buddy-skills/setup)<a href="https://agentmods.dev/skills/timothyhan/qa-buddy-skills/setup"><img src="https://agentmods.dev/badge/skills/timothyhan/qa-buddy-skills/setup.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.00096 | $0.02030 |
| Opus 5 | $0.00048 | $0.01015 |
| Sonnet 5 | $0.00019 | $0.00406 |
| Haiku 4.5 | $0.00010 | $0.00203 |
Grade B, and why
setup scanned grade B 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -r "atlassian" ~/.claude/settings.json .claude/settings.json .claude/settings.local.json 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qa-setup: QABuddy Configuration
Configure QABuddy for this project. Creates .qabuddy.json at the project root
with your preferences. All other skills read this config to adjust their behavior.
Constraints
- Never overwrite without asking. If
.qabuddy.jsonexists, show current config first. - Verify before saving. Show the full config and confirm before writing the file.
- One question at a time. Don't batch questions.
Phase 1: Check Existing Config
cat .qabuddy.json 2>/dev/null
- If config exists: Show it and ask: "Want to reconfigure or keep current settings?"
- (A) Reconfigure — proceed to Phase 2
- (B) Keep — show summary and exit
- If no config: Proceed to Phase 2
Phase 2: Context Source
Ask the SDT:
"How does your team provide feature context (epic details, acceptance criteria, specs)?"
- (A) Jira (recommended if using Atlassian) — I'll query tickets via Atlassian MCP
- (B) Specification documents — feature specs live as files in this repo (e.g.,
docs/,specs/) - (C) Chat — you'll paste or link context when needed
- (D) Custom — describe your method
If Jira: Ask for the project key (e.g., "PROJ"). Verify Jira MCP connectivity:
# Check if atlassian MCP is configured
grep -r "atlassian" ~/.claude/settings.json .claude/settings.json .claude/settings.local.json 2>/dev/null
If MCP not found, warn but don't block — SDT can set it up later.
Features and stories use Jira keys as KB identifiers (e.g., PROJ-123, PROJ-456).
If Spec, Chat, or Custom: Explain naming:
"Since you're not using Jira, you'll name features and stories yourself when running skills.
Use short, descriptive slugs (e.g., auth-system, login-page, pdf-export).
These become directory names in the knowledge base:
features-kb/features/auth-system/test-cases/login-page.md"
If Custom: Also ask for a brief description of the method (stored in config).
Phase 3: Team Mode
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 219 lines · 96 tokens per session scan B b50d65f1062d
setup is a skill published in the GitHub repository TimothyHan/qa-buddy-skills (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 96 tokens to every session and 2,030 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pptx
从论文、大纲或结构化文本生成 PowerPoint (.pptx) 演示文稿。Use when 用户需要把一篇论文/文章/大纲做成幻灯片、slides、演示文稿、PPT、deck。Don't use when 只需纯文本总结、生成 Word/PDF、或修改已有 pptx 的单个像素级样式。.
ai-style
当任务是用中文撰写或改写面向读者的文案（产品发布稿、公众号文章、邮件、README 等）， 或用户反馈文字「AI 味太重」「不像人写的」时，加载本 Skill。.
triage
你是当前任务的分诊协调者。先识别用户的全部目标、顺序依赖和验收条件，再按 “事实检索 → 计算/执行 → 写作”顺序逐步请求切换到需要的专业能力。不要替专业 能力完成它的工作，也不要在信息缺失时臆造结果。.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
coding
编写并运行 Python 代码，验证脚本逻辑和输出。.
data_analysis
基于已确认数据执行可审计的数学计算和描述统计。.