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 RBraga01/Quality-Engineering-Skills --skill is-is-not-scopinggit clone --depth 1 https://github.com/RBraga01/Quality-Engineering-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/rbraga01/quality-engineering-skills/is-is-not-scoping)<a href="https://agentmods.dev/skills/rbraga01/quality-engineering-skills/is-is-not-scoping"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/is-is-not-scoping/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/rbraga01/quality-engineering-skills/is-is-not-scoping"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/is-is-not-scoping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01793 |
| Opus 5 | $0.00034 | $0.00897 |
| Sonnet 5 | $0.00013 | $0.00359 |
| Haiku 4.5 | $0.00007 | $0.00179 |
Grade A, and why
is-is-not-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 11d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Is/Is-Not Problem Scoping
When to use
Use Is/Is-Not at the start of any quality investigation to precisely define what the problem IS and what it IS NOT. This scoping prevents wasted investigation effort and immediately eliminates hypotheses that cannot explain the observed IS/IS-NOT pattern.
Most effective in 8D D2 (problem description), CAPA scoping, and any situation where the defect is intermittent, batch-specific, or location-specific.
Critical rule — facts only
The IS column contains only documented, measured facts. Hypotheses, assumptions, and opinions belong in the hypothesis list, not in the matrix. If a cell contains an assumption rather than a fact, the entire analysis is compromised.
If data is not yet available: mark the cell as "Unknown — to be investigated" and identify what investigation is needed before proceeding.
Required Is/Is-Not Checklist
☐ All five dimensions completed — What, Which, Where, When, How many — or marked "Unknown — to be investigated" ☐ IS column contains only documented facts and measured values — no assumptions, no hypotheses ☐ IS NOT column completed for each dimension — this is where hypotheses get eliminated; do not leave blank ☐ Vague IS statements converted to specific facts with numbers (batch, quantity, percentage) ☐ At least three hypotheses generated and tested against the full matrix ☐ Eliminated hypotheses documented with the specific IS/IS-NOT entry that contradicts them ☐ Is/Is-Not output referenced in the NCR problem description and carried forward to Fishbone or 5-Why
The Is/Is-Not Matrix
Work through each dimension. For each: what DO you observe? What do you specifically NOT observe?
What
| IS | IS NOT |
|---|---|
| The specific defect observed (with measurement if applicable) | Similar defects that are NOT present |
| The affected feature, characteristic, or function | Features that are fine |
Example: "IS: Connector pin bent at 15° (pin 3 only). IS NOT: Other pins bent, housing cracked, electrical failure."
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.
- 11d ago First seen · 173 lines · 67 tokens per session scan A 1614fe316a59
is-is-not-scoping is a skill published in the GitHub repository RBraga01/Quality-Engineering-Skills (28 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 1,793 once invoked, about $0.0003 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
performance-analysis
Comprehensive performance analysis, bottleneck detection, and optimization recommendations for Claude Flow swarms.
agent-refinement
Agent skill for refinement - invoke with $agent-refinement.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agent-performance-analyzer
Agent skill for performance-analyzer - invoke with $agent-performance-analyzer.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.