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 GaZmagik/iso-24495 --skill iso-24495-2git clone --depth 1 https://github.com/GaZmagik/iso-24495Wrote 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/gazmagik/iso-24495/iso-24495-2)<a href="https://agentmods.dev/skills/gazmagik/iso-24495/iso-24495-2"><img src="https://agentmods.dev/badge/skills/gazmagik/iso-24495/iso-24495-2/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/gazmagik/iso-24495/iso-24495-2"><img src="https://agentmods.dev/badge/skills/gazmagik/iso-24495/iso-24495-2.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.00040 | $0.02244 |
| Opus 5.5 | $0.00016 | $0.00898 |
| Sonnet 5.5 | $0.00008 | $0.00449 |
| Haiku 4.5 | $0.00004 | $0.00224 |
Grade A, and why
iso-24495-2 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ISO 24495-2:2025 - Plain Language (Legal Communication)
Proxy status: These rules are this project's own proxies for the standard's principles, not its text. Following them is never a claim of ISO conformance.
Extends ISO 24495-1:2023 for legal documents, contractual provisions, licenses, and regulatory compliance.
Scope & Execution Boundaries
-
Thinking Block Exemption:
- Internal reasoning and legal analysis within thinking blocks (the
thoughtandthinkingtags) are 100% exempt from plain language constraints. - Reason exhaustively within thinking blocks. Apply plain language rules strictly to final user-facing legal text.
- Internal reasoning and legal analysis within thinking blocks (the
-
Legal Enforceability Primacy:
- Plain language simplification must never alter legal rights, liabilities, or contractual enforceability. If a term of art is legally required to avoid ambiguity, retain it and provide a plain explanation.
-
Document Design Applies Here Too:
- A legal document is a document, so
iso-24495-5loads alongside this skill. Part 5 governs headings, navigation, chunking, signalling, and readers who cannot see the page. - Four of the rules below cover what Part 5 leaves out: defined terms, cross-references, clause identifiers, and the summary layer. The fifth, section names, adds nothing and applies a case Part 5 already allows to the sections a contract has.
- Where the two appear to conflict, follow the resolution named in the rules below.
- A legal document is a document, so
Quantitative Rules & Hard Constraints (User-Facing Output)
-
Modal Verb Standardisation:
- Use must for mandatory obligations ("The User must pay...").
- Use must not for prohibitions ("The User must not copy...").
- Use may for discretionary permissions, as in "the User may end the agreement".
- Banned Words: Never use "shall", "should", "hereby", "hereinafter", "wherefore", or "parties of the first part".
-
Explicit Subject Actor Identification:
- Every obligation sentence MUST explicitly name the subject actor ("The Licensee must notify..." rather than "Notice must be provided...").
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.
- 1mo ago Changed · +65 lines 87112f219598
- 2mo ago First seen · 68 lines · 40 tokens per session scan A 003ebcca78f7
iso-24495-2 is a skill published in the GitHub repository GaZmagik/iso-24495 (201 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 2,244 once invoked, about $0.0002 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-30.
Other skills, from other repositories
plagiarism-checker
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
revenue-recognition
Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms…
privacy-and-data-protection
Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request…
benefits-and-leave
Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.
compensation-and-leveling
Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review…
employment-compliance
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a…