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 vda-6-3-auditgit 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/vda-6-3-audit)<a href="https://agentmods.dev/skills/rbraga01/quality-engineering-skills/vda-6-3-audit"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/vda-6-3-audit/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/vda-6-3-audit"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/vda-6-3-audit.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.00106 | $0.02501 |
| Opus 5 | $0.00053 | $0.01251 |
| Sonnet 5 | $0.00021 | $0.00500 |
| Haiku 4.5 | $0.00011 | $0.00250 |
Grade A, and why
vda-6-3-audit 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VDA 6.3 Process Audit
When to use
Use this skill when:
- Conducting a VDA 6.3 process audit at a supplier or internally
- Preparing for an OEM process audit visit (BMW, VW, Audi, Mercedes, Porsche, Stellantis)
- Auditing a new supplier during qualification
- Responding to a customer concern by conducting a focused process audit
- Evaluating a supplier's manufacturing process capability before SOP
Prerequisites
- Customer audit scope (which process/product to audit)
- VDA 6.3 question catalogue (the auditor works from the standard questions)
- Process Flow Diagram, PFMEA, Control Plan, and Work Instructions for the audited process
- Access to the production area, equipment records, personnel, and quality records
Workflow
Step 1 — VDA 6.3 Structure Overview
VDA 6.3 is organised into 7 process elements (P1–P7):
| Element | Name | Applies to |
|---|---|---|
| P1 | Potential Analysis | New suppliers — evaluates readiness before series production |
| P2 | Project Management | APQP and product/process development process |
| P3 | Planning the Product and Process Development | Design and process planning activities |
| P4 | Supplier Management (Purchasing) | Sub-supplier control and qualification |
| P5 | Process Input / Series | Incoming materials and components |
| P6 | Process Execution / Customer Satisfaction / Service | The manufacturing process itself |
| P7 | Customer Support / Customer Satisfaction / Service | Delivery performance, escalation, field support |
For a focused series production audit (most common): P5, P6, P7 are mandatory. P1–P4 are added for new supplier qualification or product launch audits.
Step 2 — Rating system
Every question in VDA 6.3 is scored on a 0–10 scale:
| Score | Meaning |
|---|---|
| 10 | All requirements fulfilled — systematic, effective, and documented evidence exists |
| 8 | Requirement largely fulfilled — minor gaps, no systematic risk |
| 6 | Requirement partially fulfilled — deviations exist, limited risk |
| 4 | Requirement insufficiently fulfilled — significant gaps, risk to quality |
| 2 | Requirement not fulfilled — systematic failure, high risk |
| 0 | Not applicable OR not fulfilled with no evidence |
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 · 234 lines · 106 tokens per session scan A 6bde620d5db4
vda-6-3-audit is a skill published in the GitHub repository RBraga01/Quality-Engineering-Skills (28 stars, last pushed 2d ago), licensed MIT. It adds 106 tokens to every session and 2,501 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-08-30.
Other skills, from other repositories
aqe-ruflo
Add optional Ruflo development-time orchestration to an Agentic QE workflow. Use when a task benefits from coordinated swarms, persistent cross-session memory, routing, or Ruflo hooks. Do not use for a one-shot edit, and never add Ruflo to shipped AQE runtime dependencies.
aqe-plan-work
Build dependency-aware execution plans for complex Agentic QE, Ruflo, integration, migration, or multi-stream engineering programs. Use when Codex must turn research or requirements into phased work, select a small AQE fleet, map critical paths and parallel streams, define acceptance gates, or sequence risky changes.…
aqe-research
Conduct evidence-first technical research for Agentic QE, Ruflo, related ruvnet projects, or external tools. Use when Codex must investigate a repository, compare current upstream changes, trace dependencies and history, distinguish verified facts from inference, or synthesize findings into actionable engineering…
aqe-plan-quality
Create risk-based quality and test plans for Agentic QE changes. Use when scoping a feature, translating requirements into verification work, selecting QE specialties, assessing testability, or deciding which .claude/agents/v3/qe-.md capabilities should inform a task. Do not use merely to execute an already-defined…
aqe-test-change
Design, implement, and run durable tests for Agentic QE code changes. Use when adding tests, reproducing a defect, filling a coverage gap, selecting affected Vitest suites, checking CLI/MCP parity, or verifying a fix in this repository. Do not use for a read-only quality review with no requested edits.
aqe-review-quality
Review Agentic QE changes and issue an evidence-backed quality verdict. Use for code review, regression-risk assessment, release readiness, quality-gate evaluation, security/performance/testability review, or checking whether a change has sufficient verification. Do not use when the user primarily asks to implement a…