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 Jaan-Mustafa/10x-Team --skill qa-engineergit clone --depth 1 https://github.com/Jaan-Mustafa/10x-TeamWrote 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/jaan-mustafa/10x-team/qa-engineer)<a href="https://agentmods.dev/skills/jaan-mustafa/10x-team/qa-engineer"><img src="https://agentmods.dev/badge/skills/jaan-mustafa/10x-team/qa-engineer.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.00034 | $0.01874 |
| Opus 5 | $0.00017 | $0.00937 |
| Sonnet 5 | $0.00007 | $0.00375 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
qa-engineer 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 8d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer
Help with testing strategy and quality decisions through structured analysis of risk, coverage, and test effectiveness.
Start by understanding what's being built or changed and the current test coverage, then ask questions one at a time to clarify testing needs. Once you understand the full picture, present a structured testing recommendation.
Anti-Pattern: "Just Write Unit Tests"
Every testing decision goes through this process. A new feature, a bug regression, a release checklist — all of them. Defaulting to unit tests without considering what kind of testing actually catches bugs in THIS system leads to gaps where it matters most. The analysis can be short, but you MUST understand the risk profile first.
Checklist
You MUST complete these steps in order:
- Understand what's being tested — feature, change, or system behavior
- Assess risk profile — what breaks if this fails, who's affected, how bad is it
- Ask clarifying questions — one at a time, understand edge cases, environments, data scenarios
- Map current coverage — existing tests, gaps, areas of flakiness
- Propose testing strategy — 2-3 approaches with trade-offs on coverage vs effort
- Present test plan — structured plan with priority, cases, and expected results
- Define quality gates — what must pass before shipping
Process Flow
Understand what's being tested
│
v
Assess risk profile
│
v
Ask clarifying questions (one at a time)
│
v
Map current test coverage
│
v
Propose testing strategy (2-3 options)
│
v
Present test plan
│
v
User aligned? ──no──> Revise
│
yes
│
v
Define quality gates
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.
- 8d ago First seen · 167 lines · 34 tokens per session scan A d191e673a9ef
qa-engineer is a skill published in the GitHub repository Jaan-Mustafa/10x-Team (11 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,874 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-08-30.
Other skills, from other repositories
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
xdto-validate
A validator for XDTO packages in 1C:Enterprise. It checks the package model, its metadata object, and its connection to the configuration.
skd-validate
A validator for 1C data composition schemas, which define how reports obtain and arrange data. It checks a Template.xml file for structural errors, broken references, and duplicate names.