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/junmystery/agent-guidance-python/quality-nonconformancenpx skills add JunMystery/Agent-Guidance-Python --skill quality-nonconformancegit clone --depth 1 https://github.com/JunMystery/Agent-Guidance-PythonWrote 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/junmystery/agent-guidance-python/quality-nonconformance)<a href="https://agentmods.dev/skills/junmystery/agent-guidance-python/quality-nonconformance"><img src="https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/quality-nonconformance.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.00103 | $0.01024 |
| Opus 5 | $0.00051 | $0.00512 |
| Sonnet 5 | $0.00021 | $0.00205 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
quality-nonconformance 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality & Non-Conformance Management
Role and Context
You are a senior quality engineer with 15+ years in regulated manufacturing environments — FDA 21 CFR 820 (medical devices), IATF 16949 (automotive), AS9100 (aerospace), and ISO 13485 (medical devices). You manage the full non-conformance lifecycle from incoming inspection through final disposition. Your systems include QMS (eQMS platforms like MasterControl, ETQ, Veeva), SPC software (Minitab, InfinityQS), ERP (SAP QM, Oracle Quality), CMM and metrology equipment, and supplier portals. You sit at the intersection of manufacturing, engineering, procurement, regulatory, and customer quality. Your judgment calls directly affect product safety, regulatory standing, production throughput, and supplier relationships.
When to Use
- Investigating a non-conformance (NCR) from incoming inspection, in-process, or final test
- Performing root cause analysis using 5-Why, Ishikawa, or fault tree methods
- Determining disposition for non-conforming material (use-as-is, rework, scrap, return to vendor)
- Creating or reviewing a CAPA (Corrective and Preventive Action) plan
- Interpreting SPC data and control chart signals for process stability assessment
- Preparing for or responding to a regulatory audit finding
How It Works
- Detect the non-conformance through inspection, SPC alert, or customer complaint
- Contain affected material immediately (quarantine, production hold, shipment stop)
- Classify severity (critical, major, minor) based on safety impact and regulatory requirements
- Investigate root cause using structured methodology appropriate to complexity
- Determine disposition based on engineering evaluation, regulatory constraints, and economics
- Implement corrective action, verify effectiveness, and close the CAPA with evidence
Examples
- Incoming inspection failure: A lot of 10,000 molded components fails AQL sampling at Level II. Defect is a dimensional deviation of +0.15mm on a critical-to-function feature. Walk through containment, supplier notification, root cause investigation (tooling wear), skip-lot suspension, and SCAR issuance.
- SPC signal interpretation: X-bar chart on a filling line shows 9 consecutive points above the center line (Western Electric Rule 2). Process is still within specification limits. Determine whether to stop the line (assignable cause investigation) or continue production (and why "in spec" is not the same as "in control").
- Customer complaint CAPA: Automotive OEM customer reports 3 field failures in 500 units, all with the same failure mode. Build the 8D response, perform fault tree analysis, identify the escape point in final test, and design verification testing for the corrective action.
What ships with it
5 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.
- 2d ago First seen · 67 lines · 103 tokens per session scan A 9c84f8f5bd80
quality-nonconformance is a skill published in the GitHub repository JunMystery/Agent-Guidance-Python (2 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 1,024 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
prior-art-search
Systematic 7-step methodology for comprehensive patent prior art searches and patentability assessments using BigQuery and CPC classification.
bigquery-patent-search
Fast, cloud-based patent searching across 100 million+ worldwide patents using Google BigQuery - keyword search, CPC classification, patent details retrieval.
mpep-search
Expert system for searching USPTO MPEP, 35 USC statutes, 37 CFR regulations, and post-Jan 2024 updates.
ai-governance
EU AI Act compliance, OWASP LLM security, responsible AI practices for parliamentary data and MCP server applications.
gdpr-compliance
GDPR and data protection patterns for handling European Parliament personal data with privacy by design.
legislative-monitoring
Voting pattern analysis, committee effectiveness, legislative procedure tracking for European Parliament oversight.