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 FlyFission/nuclear-grade-context-engineering --skill checking-legal-and-safety-wordinggit clone --depth 1 https://github.com/FlyFission/nuclear-grade-context-engineeringWrote 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/flyfission/nuclear-grade-context-engineering/checking-legal-and-safety-wording)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/checking-legal-and-safety-wording"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/checking-legal-and-safety-wording/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/flyfission/nuclear-grade-context-engineering/checking-legal-and-safety-wording"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/checking-legal-and-safety-wording.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.00081 | $0.01014 |
| Opus 5 | $0.00041 | $0.00507 |
| Sonnet 5 | $0.00016 | $0.00203 |
| Haiku 4.5 | $0.00008 | $0.00101 |
Grade A, and why
checking-legal-and-safety-wording 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 12d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checking Legal and Safety Wording
Overview
This skill keeps two things apart: what the MIT license lets people do, and what the repo proves. People may use the repo. But using it does not create formal verification and validation, compliance, certification, safety, security, or fitness for regulated use.
Decision contract
- Claim checked: public text stays inside the assurance boundary -- "you may use it" kept apart from "it is proven fit", banned claim phrases only in negative or disclaimer sentences, and
python tools/ng.py doctor .passes. - Artifact observed: the changed public text against
LICENSE,DISCLAIMER.md,SECURITY.md, andcompliance-boundaries.md-> bounded wording, updated docs/templates, and the scan results or list of gaps. - Decision affected: block -- whether public text stays inside the assurance boundary; an overreaching license/safety/compliance claim blocks until reworded.
- Failure class: assurance-overreach (public copy promising safe, secure, compliant, approved, or certified results the repo has not proven).
- Next action: reword to evidence-tied wording before release; requests for legal advice or regulated-use approval escalate to a qualified professional.
When to Use
- You are editing the README, install docs, public docs, templates, skills, commands, examples, or release notes.
- You are adding source families, assurance-sounding wording, or enterprise rollout wording.
- You are getting the repo ready to be public.
- A public claim needs a self-check before release, or a line that points hard claims to a qualified outside review.
When Not to Use
- The work is a private detail with no public-use wording.
- The user needs legal advice; point them to a qualified lawyer.
Inputs
- The changed public text.
LICENSE,DISCLAIMER.md,SECURITY.md, anddocs/00-standards-foundation/compliance-boundaries.md.- The checker's starting list of banned claim phrases.
Process
- Confirm the license wording is still MIT.
- Keep "you may use it" separate from "it is proven fit."
- Self-check the exact claim against the evidence you have and against a qualified authority.
- Add clear "this does not create..." wording near onboarding, templates, commands, and command-line help.
- Swap broad assurance words for wording tied to evidence anyone can review.
- Scan the public text for banned phrases and for leftover internal text.
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.
- 12d ago First seen · 99 lines · 81 tokens per session scan A 0731b07e5847
checking-legal-and-safety-wording is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 1,014 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
contextlock
Safely inspect a repository through the ContextLock MCP server. Use when exploring, searching, reviewing, or auditing repository files with ContextLock, especially before reading unfamiliar code or when sensitive files and secrets may be present.
html-ppt-zhangzara-stencil-tablet
A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.
dependency-audit
Audits direct and transitive dependencies for license compliance, maintenance health, CVEs, abandoned packages, and bloat. Triggers on: "audit dependencies", "license check", "dependency health", "abandoned packages", "unused dependencies", "license compliance", "supply chain", "dependency risk".
audit-licenses
Use to list the open-source licenses of every dependency in this project, grouped by license family. Flags GPL or AGPL dependencies that may force the project itself to be open-source. Triggers on /audit-licenses.
afrexai-compliance-engine
Your AI compliance officer. Guides startups and scale-ups through SOC 2, ISO 27001, GDPR, HIPAA, and PCI DSS — from zero to audit-ready. No consultants needed.
civic-publish-gate
Run deterministic source, citation, freshness, privacy, meeting-certainty, accessibility, correction-state, and human-approval checks before civic publication.