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-stylegit 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-style)<a href="https://agentmods.dev/skills/gazmagik/iso-24495/iso-24495-style"><img src="https://agentmods.dev/badge/skills/gazmagik/iso-24495/iso-24495-style/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-style"><img src="https://agentmods.dev/badge/skills/gazmagik/iso-24495/iso-24495-style.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.01440 |
| Opus 5 | $0.00020 | $0.00720 |
| Sonnet 5 | $0.00008 | $0.00288 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
iso-24495-style 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ISO 24495 Response Style
Claude Code carries these rules as an output style, which applies to every response without being asked. Codex has no equivalent, so the same rules ship here as a skill.
To apply them to every response, name this skill in your AGENTS.md:
Apply the `iso-24495-style` skill to every response.
Put that in your project's AGENTS.md or in ~/.codex/AGENTS.md. A plugin
cannot apply itself: an AGENTS.md inside a plugin is ignored. For a single
reply, invoke $iso-24495-style instead.
The rules below are the shipped output style, word for word. A test keeps the two identical, so neither can drift from the other.
You must apply the plain-language principles of ISO 24495-1 in all responses, as interpreted by the ISO 24495 skills. Their rules are proxies for the standard, not its text, and never a conformance claim. Invoke the skills relevant to the task at hand:
iso-24495-1: The core standard; governs every response.iso-24495-2: Legal writing: contracts, licences, compliance text.iso-24495-3: Science and technical writing: documentation, architecture, code review.iso-24495-4: Organisational implementation (provisional): gap analysis, plain language policy, review workflows, readiness for the future published standard. Never for writing individual documents.iso-24495-5: Document design (provisional): structuring complex multi-section documents.iso-24495-text-audit: User-invoked text audit. Never invoke it automatically.
The standard's four governing principles: readers get the information they need (relevant), can find it (findable), can understand it (understandable), and can act on it (usable).
Core requirements:
- Relevance: Serve the reader in front of you. Match vocabulary and depth to what they know and what they must do next.
- Clarity: Use familiar words over formal ones. Trim filler:
to, notin order to;because, notdue to the fact that. Keep technical terms the reader's field expects; define the rest on first use. - Directness: Default to the active voice; passive is fine when the actor is unknown or beside the point. Address the reader as you. Front-load the main point.
- Sentence discipline: Keep the average at or under 20 words per sentence, aiming for 15 to 20 in longer prose; treat 30 as the hard ceiling for any single sentence. Keep subject and verb together. Vary length for rhythm.
- Structure (findability): Use clear headings, bullet points, and numbered lists. Prefer paragraphs of 3 to 5 sentences on one topic; a single-sentence paragraph is fine, and only paragraphs beyond 5 count as violations.
- Positive framing: Say what to do rather than what to avoid, unless the warning is the point.
- Consistency: Use the same term for the same concept throughout. Repetition beats elegant variation.
- Explicit connections (usability): State relationships with because, therefore, if, before, after; never leave the reader to infer them.
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.
- 12d ago First seen · 88 lines · 40 tokens per session scan A 4ae0d6004e34
iso-24495-style is a skill published in the GitHub repository GaZmagik/iso-24495 (171 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,440 once invoked, about $0.0002 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
iso-24495
Use when text must be easy for its intended reader to find, understand, and act on — reports, emails, documentation, UI text, announcements, explanations, AI output that reads as dense or bureaucratic. Applies ISO 24495-1 plain language principles with dedicated technique layers for English and Traditional Chinese.…
radin-execute
Work through a project's whole backlog: prioritize every task, execute each via a sub-agent, commit after each. Use when the user wants the entire backlog processed ("work through my backlog"), not one named task. Delegates all implementation to sub-agents; clarifies ambiguity by asking the user rather than guessing.
radin-record
Log feedback, bugs, follow-ups, or ideas raised mid-session as structured backlog entries, so they survive past the conversation. Use for /radin-record, "log this to the backlog", "add as follow-up/bug/idea", "record what we just found", "note this for later", "add findings to backlog". Triggers even on vague asks…
radin-plan
Write a step-by-step implementation plan for one backlog entry, without touching code. Scope is one task (a title/keyword), not the whole backlog. Use for /radin-plan, "plan this backlog entry", "write a plan for X before we execute it". radin-execute delegates here for any entry too complex to implement directly.
radin-review
Run a thermo-nuclear code quality review over a scope (commit, PR, directory, or a range like "since yesterday"), triage the findings with the user, and log the ones they keep as backlog entries instead of printing to terminal. Use for /radin-review, "review and log to backlog", "audit this commit/PR/directory and…
radin-doctor
Check that radin's own install under /.claude is complete and its optional companion tools are reachable. Use for /radin-doctor, "check my radin install", "is radin installed correctly", "radin doctor", "verify radin install".