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/jarroslav/agentic-os/qa-scopingnpx skills add Jarroslav/agentic-os --skill qa-scopinggit clone --depth 1 https://github.com/Jarroslav/agentic-osWrote 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/jarroslav/agentic-os/qa-scoping)<a href="https://agentmods.dev/skills/jarroslav/agentic-os/qa-scoping"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/qa-scoping.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.00118 | $0.02240 |
| Opus 5 | $0.00059 | $0.01120 |
| Sonnet 5 | $0.00024 | $0.00448 |
| Haiku 4.5 | $0.00012 | $0.00224 |
Grade A, and why
qa-scoping 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 5d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qa-scoping
Everything QA between "we know what we are building" and "the health record is current": decide what must be tested, judge what was tested, write down what changed.
Prerequisites: .agentic/guides/testing/qa-strategy.md and .agentic/guides/testing/qa-health.md
must already exist. If either is missing, halt with:
[QA GUIDE MISSING] .agentic/guides/testing/qa-strategy.md not found.
Run the `qa-baseline` skill to generate the QA knowledge foundation first.
Both documents this skill writes are specified in
references/qa-artifacts.md. Follow it exactly — the pipeline and the Phase 7
reviewer parse what comes out.
Every mode takes the same two arguments: run_dir (absolute) and merge_base
(origin/main unless told otherwise).
Methodology owner. What a well-shaped test case set covers is defined by the
test-casesblueprint inagentic-qe(skills/qe-blueprints/references/catalog/design/test-cases.md). This skill executes; the blueprint is the authority on method. If the two ever disagree, the blueprint wins and this file is what gets corrected — one source of truth, so two agents cannot follow two different sets of practices.
Mode: --checklist (Phase 6)
Runs before implementation. The output is a claim about what this change has to get right, made while it is still cheap to disagree.
Gather the inputs
Read, in this order: <run_dir>/requirements.md (required — halt if absent),
<run_dir>/design.md (skip if absent), then
.agentic/guides/testing/qa-strategy.md and
.agentic/guides/testing/qa-health.md.
Work out what this change touches
From the requirements, name four things:
- Modules — the paths, packages or domains the work lands in.
- Surfaces users meet — endpoints, screens, commands.
- Risk flags — auth, payments, data migration, security, breaking change.
- Search terms — three to six words (class, endpoint, domain nouns) good enough to find existing tests with.
What ships with it
2 files 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.
- 5d ago First seen · 220 lines · 118 tokens per session scan A 30b4c58cdfa0
qa-scoping is a skill published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 118 tokens to every session and 2,240 once invoked, about $0.0006 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 skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.