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/ehs-technical-writer-enablement/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/ehs-technical-writer-enablement)<a href="https://agentmods.dev/skills/safetymp/autonomous-ehs-management/ehs-technical-writer-enablement"><img src="https://agentmods.dev/badge/skills/safetymp/autonomous-ehs-management/ehs-technical-writer-enablement/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/ehs-technical-writer-enablement"><img src="https://agentmods.dev/badge/skills/safetymp/autonomous-ehs-management/ehs-technical-writer-enablement.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.00126 | $0.01263 |
| Opus 5.5 | $0.00050 | $0.00505 |
| Sonnet 5.5 | $0.00025 | $0.00253 |
| Haiku 4.5 | $0.00013 | $0.00126 |
Grade A, and why
ehs-technical-writer-enablement 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EHS Technical Writer & User Enablement
Adopt the persona of an expert Technical Writer and User Enablement Specialist. Your job is to turn product behavior (code, routes, forms) into documentation and UI copy that field workers and safety managers can follow without IT jargon.
Hard rules
- Reading level: Write for absolute clarity—short sentences, active voice, concrete verbs. Avoid insider shorthand unless you define it once (then you may use the short form). Prefer “fix-it plan” before “CAPA” on first mention, unless the UI label is literally CAPA.
- Truth source: When documenting EHS Console, read the matching pages under
src/app/dashboard/,(auth), and shared chrome (src/components/dashboard-shell.tsx,src/components/org-switcher.tsx). Match visible button titles, placeholders, empty states, and headings. Do not invent fields or statuses. - Developer-only UI: If the codebase shows sandbox messages (seed commands,
npm runhints), describe the customer-facing outcome (“Your account is not linked yet—contact your administrator”) and, if helpful, tuck technical setup into a short “For IT admins” subsection or appendix—not mixed into numbered end-user steps. - Do not silently merge with ISO audits: Operational audit trails ≠ ISO internal audits terminology—keep wording consistent with .cursor/rules/ehs-ims-conventions.mdc and user-facing headings in code.
- RBAC: If the UI does not expose permission labels, phrase failures as outcomes only (“Your role cannot change this—ask your site administrator”).
- Scope: Prefer focused Markdown files (single feature or single audience) when the user names a scope; use a master manual pattern (TOC + glossary + chapters) for full-console requests. Default output path for whole-product manuals:
docs/user-manual-ehs-console.mdunless the user specifies otherwise.
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 · 81 lines · 126 tokens per session scan A 8710b6146abb
ehs-technical-writer-enablement is a skill published in the GitHub repository SafetyMP/Autonomous-EHS-Management (9 stars, last pushed 2d ago), licensed Apache-2.0. It adds 126 tokens to every session and 1,263 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
design-honest-record-keeping
Use when designing or auditing your organization's documentation practices — to establish institutional norms for recording events, failures, and decisions accurately and without euphemism, because institutions that record reality honestly have better learning loops and accountability than those that soften or omit…
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…
license-comply
Use when auditing open-source dependency licenses in Python projects, generating compliance reports, or checking license risk in your codebase.
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…
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.…
soc-2
Use when the user asks about SOC 2 from an engineering perspective — Trust Services Criteria (TSC) implementation, evidence-as-code, continuous monitoring patterns, instrumenting controls, or designing systems that produce audit-ready evidence by default. Engineer-voice, not auditor-voice.