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 ppapgit 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/ppap)<a href="https://agentmods.dev/skills/rbraga01/quality-engineering-skills/ppap"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/ppap.svg" alt="Measured on agentmods" 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.00085 | $0.02267 |
| Opus 5 | $0.00043 | $0.01133 |
| Sonnet 5 | $0.00017 | $0.00453 |
| Haiku 4.5 | $0.00009 | $0.00227 |
Grade A, and why
ppap 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Part Approval Process (PPAP)
When to use
Use this skill when:
- A supplier must submit parts for customer approval before Start of Production (SOP)
- A design change, process change, or engineering change requires re-submission
- An OEM or Tier 1 customer requests a PPAP at a specific level
- Reviewing or auditing an incoming PPAP package from a supplier
- Determining what PPAP level is required for a given change
Prerequisites
- Part number, revision level, and customer drawing
- Bill of Materials (BOM) if applicable
- Production process flow and manufacturing location confirmed
- Customer's PPAP level requirement (Level 1–5) or change category known
Workflow
Step 1 — Determine the PPAP Level
| Level | What must be submitted |
|---|---|
| 1 | Part Submission Warrant (PSW) only — no supporting documents unless requested |
| 2 | PSW + designated samples + limited supporting data |
| 3 | PSW + product samples + complete supporting data (default for new parts) |
| 4 | PSW + other requirements as defined by the customer |
| 5 | PSW + parts and complete supporting data — reviewed at the supplier's manufacturing location |
Default: Level 3 for new parts or significant changes. Always confirm with the customer before submitting.
Step 2 — Identify the change category
PPAP re-submission is required for:
- New part or product
- Engineering change (design revision)
- Change of supplier (sub-supplier, raw material)
- Change of manufacturing location, process, or tooling
- Change that affects fit, form, or function
- Corrective action following a field failure or customer complaint
- Production interruption >12 months
Step 3 — Prepare all 18 PPAP elements
Production trial run minimum: Unless otherwise specified in writing by the authorised customer representative, the production trial run must consist of a minimum of 300 consecutive parts produced at the production rate, using production tooling, production process, production operators, and production tooling (AIAG PPAP 4th ed §4.0). This run generates the PPAP samples (Element 14), dimensional results (Element 9), and capability data (Element 11). A run shorter than 300 consecutive parts requires explicit written customer authorisation before PSW can be signed.
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.
- 8d ago First seen · 232 lines · 85 tokens per session scan A aaa0509e4e5b
ppap is a skill published in the GitHub repository RBraga01/Quality-Engineering-Skills (28 stars, last pushed 4d ago), licensed MIT. It adds 85 tokens to every session and 2,267 once invoked, about $0.0004 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
execute
Run the generated Playwright tests and summarize pass/fail results. Use when the user wants to run the tests produced by /verefi:implement, check whether a test plan's acceptance criteria are met, or debug failing Verefi-generated tests.
ai-augmented-testing
When the user wants to evaluate, adopt, or operate AI-augmented testing tools and approaches — autonomous test generation, self-healing locators, AI-assisted authoring, vision-based testing, agentic test runners. Use when the user mentions "AI testing," "AI-augmented testing," "Testim," "Mabl," "Functionize,"…
ci-test-orchestration
When the user wants to design, audit, or optimize how tests run in CI — sharding, matrix builds, parallelism, retry policy, test selection, artifact handling, and gate strategy. Use when the user mentions "CI test orchestration," "test sharding," "matrix builds," "parallel tests in CI," "GitHub Actions matrix,"…
cucumber-gherkin
When the user wants to design, implement, debug, or evolve BDD scenarios using Cucumber and the Gherkin syntax across any language (Java, JS, Ruby, JVM, etc.). Use when the user mentions "Cucumber," "Gherkin," "Given/When/Then," ".feature file," "step definitions," "scenario outline," "data tables," "Cucumber hooks,"…
junit-testng
When the user wants to design, implement, debug, or optimize JUnit 5 (Jupiter) or TestNG tests on the JVM. Use when the user mentions "JUnit 5," "JUnit Jupiter," "@Test," "@ParameterizedTest," "@MethodSource," "@TestFactory," "TestNG," "@DataProvider," "@BeforeEach," "@BeforeMethod," "AssertJ," "Hamcrest," "Mockito,"…
llm-eval-testing
When the user wants to design, build, or operate evaluations (evals) for LLM-powered products — chatbots, RAG systems, agents, classification, summarization, structured output. Use when the user mentions "LLM evals," "evals," "RAG evaluation," "RAGAS," "DeepEval," "LangSmith," "LangFuse," "PromptLayer," "OpenAI…