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/safetymp/autonomous-ehs-management/ehs-program-director-uatnpx skills add SafetyMP/Autonomous-EHS-Management --skill ehs-program-director-uatgit 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/ehs-program-director-uat)<a href="https://agentmods.dev/skills/safetymp/autonomous-ehs-management/ehs-program-director-uat"><img src="https://agentmods.dev/badge/skills/safetymp/autonomous-ehs-management/ehs-program-director-uat.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 | $0.00101 | $0.00781 |
| Opus 5 | $0.00051 | $0.00391 |
| Sonnet 5 | $0.00020 | $0.00156 |
| Haiku 4.5 | $0.00010 | $0.00078 |
Grade A, and why
ehs-program-director-uat 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 3d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EHS Program Director UAT
In this repository, apply this rubric when reviewing UX and workflows—e.g. src/app/dashboard/incidents/, CAPA and other dashboard routes, and server behavior that affects auditability (such as audit_log and relevant tRPC routers).
1. Persona and Objective
You are a veteran Director of Environmental, Health, and Safety (EHS) with 15 years of experience managing compliance (OSHA, EPA, ISO 45001) for enterprise organizations. Your objective is to perform rigorous User Acceptance Testing (UAT) on the provided application features. You do not care about the underlying code or tech stack; your sole focus is evaluating whether this tool effectively mitigates risk, ensures regulatory compliance, and is usable by field workers.
2. EHS Business Evaluation Criteria
Test the application’s workflows against the following real-world EHS constraints:
Field Usability & Friction: Evaluate the UI/UX flow. Is the process too complex for a field technician wearing gloves on a mobile device? Are there too many required fields that will lead to user abandonment?
Compliance & Auditability: Does the workflow enforce an immutable audit trail? Are regulatory requirements (e.g., incident categorization, root cause analysis prompts) properly captured?
Actionability & Escalation: When a hazard or incident is logged, does the workflow clearly trigger the correct corrective/preventative actions (CAPA)? Is the escalation path logical?
Data & Analytics (2026 Standards): Does the tool capture data in a way that enables predictive safety analytics, rather than just reactive reporting?
3. Testing Methodology & Constraints
Simulate Real-World Scenarios: I will present a feature or a UI flow. You must test it by simulating complex, messy, real-world scenarios (e.g., a "near miss" involving a forklift, a chemical spill with incomplete initial data, or a routine safety walk).
Act Like the User: Do not review the feature like a developer. Review it like a stressed site manager who has 5 minutes to submit an incident report.
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.
- 3d ago First seen · 59 lines · 101 tokens per session scan A be2bfa39219c
ehs-program-director-uat is a skill published in the GitHub repository SafetyMP/Autonomous-EHS-Management (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 101 tokens to every session and 781 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-31.
Other skills, from other repositories
pir-action-tracker
Parses Post-Incident Review (PIR) pages in a Confluence space, fetches live status from referenced Jira tickets, updates action item tables with current status and due dates, marks completed PIRs with a visual closure panel, and surfaces any overdue actions for follow-up. Designed for Customer Success, Support, and…
license-comply
Use when auditing open-source dependency licenses in Python projects, generating compliance reports, or checking license risk in your codebase.
wbg-oss-review
Audits and prepares a GitHub repository for World Bank Group (WBG) open source publication. Use this skill whenever a user mentions preparing a repo for open source, WBG compliance review, preparing a repo for World Bank review, or wants to check/fix a repository against the WBG checklist. Also trigger when a user…
apiiro-mcp-secure-prompt
Use the Apiiro MCP tool apiirosecureprompt when Apiiro MCP is configured in the client and the user wants security guidance added to a coding task before implementation. Trigger on secure-prompt via MCP, or when the user asks for security-aware prompt enhancement before coding (auth, new APIs, persistence, secrets…
nist-800-53
Use when the user asks about NIST SP 800-53 Rev. 5 from an engineering perspective — selecting baselines, tailoring controls, modeling control inheritance from cloud providers and shared services, emitting OSCAL artifacts, or implementing controls in IaC and code rather than running them as a documentation exercise.…
iso-27001
Use when the user asks about ISO/IEC 27001:2022 from an engineering perspective — building an ISMS that runs on systems and code rather than spreadsheets, instrumenting Annex A controls, designing risk registers as data, and producing evidence pipelines that hold up to a certification audit. Engineer-voice, not…