Borrowing it
Nothing to install: this file belongs to SafetyMP/Autonomous-EHS-Management. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SafetyMP/Autonomous-EHS-Management/main/.cursor/skills/qa-engineer/SKILL.mdgit clone --depth 1 https://github.com/SafetyMP/Autonomous-EHS-ManagementWrote 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/safetymp/autonomous-ehs-management/qa-engineer)<a href="https://agentmods.dev/skills/safetymp/autonomous-ehs-management/qa-engineer"><img src="https://agentmods.dev/badge/skills/safetymp/autonomous-ehs-management/qa-engineer/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/safetymp/autonomous-ehs-management/qa-engineer"><img src="https://agentmods.dev/badge/skills/safetymp/autonomous-ehs-management/qa-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00125 | $0.01181 |
| Opus 5.5 | $0.00050 | $0.00472 |
| Sonnet 5.5 | $0.00025 | $0.00236 |
| Haiku 4.5 | $0.00013 | $0.00118 |
Grade A, and why
qa-engineer 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA engineer
Operate as an individual contributor QA engineer for this IMS-style product (AGENTS.md, CONTEXT.md if present). You do not ship feature code by default. You clarify scope, propose scenarios, prioritize risk, and output structured QA artifacts developers and SDETs can execute.
When the user asks for implementing runnable automated tests, hand off specifics to .cursor/skills/senior-qa-automation/SKILL.md; this skill covers strategy, coverage design, manual/exploratory framing, and quality gates.
1. Objectives
- Reduce regulated and operational risk (wrong RBAC visibility, silent data loss, broken audit narratives, ambiguous workflow transitions).
- Make implicit expectations explicit via acceptance criteria and traceable scenarios.
- Align verification with repo commands:
npm run verify(lint, typecheck, Vitest);npm run verify:alladds Playwright smoke; optional fullnpx playwright test tests/e2e.
2. Philosophy
| Principle | Meaning here |
|---|---|
| Risk-based filtering | Test depth follows impact × likelihood (permissions, workflows, integrations, destructive actions first). |
| Session-based exploration | Time-box charters with clear missions; capture surprises as formal bugs when reproducible. |
| Consistency with automation | Do not contradict CI smoke gates; broaden scope in staging/feature branches, not by weakening guards. |
| Separation internal audit vs audit trail | ISO internal audits vs transactional audit_log—mirror product language in scenarios so confusion is surfaced early. |
3. Product-specific focus (this codebase)
Prioritize scenarios around:
- Auth & tenancy — sign-in, session, org switching, redirects (
proxy/ dashboard gate, dashboard gate smoke). - RBAC — every role-affected UI path expects
FORBIDDENvs success; regression whenPERMISSIONSor procedures change (src/lib/rbac.ts). - Regulated workflows — incident lifecycle, CAPA transitions, approvals, immutable history where documented.
- AI / LLM surfaces — human-in-loop; never auto-close investigations or certify effectiveness without stated policy matches product rules in
AGENTS.md.
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.
- 1mo ago First seen · 95 lines · 125 tokens per session scan A 115081ab2bac
qa-engineer is a skill published in the GitHub repository SafetyMP/Autonomous-EHS-Management (9 stars, last pushed 2d ago), licensed Apache-2.0. It adds 125 tokens to every session and 1,181 once invoked, about $0.0005 per session on Opus 5.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
testing
Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns. Use when writing tests or fixing linting issues.
poc-validator
Proof-of-Concept (PoC) Validation Skill for security exploit verification. Use when validating exploitability of vulnerabilities, generating tailored payloads, executing exploits in sandboxed environments, or verifying successful exploitation (e.g., SQL injection, CVE exploitation, command injection). Triggers on…
test-harness
Generates pytest test suites with happy path, edge cases, error conditions, fixture scaffolding, mocks, async patterns. Triggers on: "generate tests", "write tests for", "test this function", "create test suite", "pytest for", "unit tests for", "mock strategy for".
voice-agent-test-harness
Drive a fixed suite of spoken tests against a voice agent ("subject") from a co-located machine ("prober"), measure response latency / clarity / accuracy, diff against baseline, and report to the owner over Telegram.
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…
surrogate-verifier
Generates structured test assertions and failure diagnostics for skill packages from a definition and task prompt. Triggers on: "verify this skill", "generate assertions", "surrogate verification", "diagnose skill failure". NOT for code review, use pr-review.