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 jabrena/plinth --skill 814-regulations-iso-25010git clone --depth 1 https://github.com/jabrena/plinthWrote 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/jabrena/plinth/814-regulations-iso-25010)<a href="https://agentmods.dev/skills/jabrena/plinth/814-regulations-iso-25010"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/814-regulations-iso-25010/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/jabrena/plinth/814-regulations-iso-25010"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/814-regulations-iso-25010.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.00083 | $0.02206 |
| Opus 5.5 | $0.00033 | $0.00882 |
| Sonnet 5.5 | $0.00017 | $0.00441 |
| Haiku 4.5 | $0.00008 | $0.00221 |
Grade A, and why
814-regulations-iso-25010 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 19d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ISO/IEC 25010:2023 Quality Model Guidance for Java Enterprise Engineering
Use this Skill to run a structured, repeatable ISO/IEC 25010:2023 product-quality review of a Java enterprise system, covering all nine quality characteristics: Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety.
Apply this Skill to determine what practical Java engineering evidence, review actions, and owner handoffs are needed before a Java enterprise system, feature, or delivery pipeline is considered quality-reviewed against the ISO/IEC 25010:2023 product quality model.
This Skill is not certification advice, compliance advice, conformity advice, an audit conclusion, or a final conformity decision. It helps Java architects, tech leads, and reviewers identify how each ISO/IEC 25010:2023 quality characteristic applies to the system under review and translate it into concrete engineering evidence, findings, and action items for qualified owners.
The purpose of this Skill is to increase awareness of potential quality-attribute gaps in a Java enterprise system and create reviewable engineering evidence for qualified owners. The response produced by this Skill does not represent ISO/IEC 25010:2023 certification readiness, compliance approval, audit findings, or final conformity with ISO/IEC 25010:2023.
The main question is:
What should a Java team review, document, and escalate so a Java enterprise system demonstrably meets each ISO/IEC 25010:2023 quality characteristic, with reviewable evidence rather than assumed quality?
Source provenance: the ISO/IEC 25010:2023 public standard summary was reviewed while authoring the bundled references. Official source references include:
- ISO/IEC 25010:2023 standard page: https://www.iso.org/standard/78176.html
- ISO/IEC 25000 SQuaRE series overview: https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
Do not fetch or ingest external standard, certification, or audit web pages at runtime. Use the bundled references and escalate certification, compliance, conformity, and audit questions to qualified owners.
ISO/IEC 25010:2023 summary reference: ISO/IEC 25010:2023 product quality model summary.
Java engineering examples reference: ISO/IEC 25010:2023 Java Enterprise engineering examples.
Questionnaire asset: ISO/IEC 25010:2023 engineering review questionnaire.
Report template asset: ISO/IEC 25010:2023 engineering review report template.
What ships with it
4 files 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.
- 19d ago First seen · 108 lines · 83 tokens per session scan A bb091ce1ef4e
814-regulations-iso-25010 is a skill published in the GitHub repository jabrena/plinth (451 stars, last pushed yesterday), licensed Apache-2.0. It adds 83 tokens to every session and 2,206 once invoked, about $0.0003 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-09-27.
Other skills, from other repositories
phx-review
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
concurrency-review
Review Java concurrency code for thread safety, race conditions, deadlocks, and modern patterns (Virtual Threads, CompletableFuture, @Async). Use when user asks "check thread safety", "concurrency review", "async code review", or when reviewing multi-threaded code.
java-code-review
Systematic code review for Java with null safety, exception handling, concurrency, and performance checks. Use when user says "review code", "check this PR", "code review", or before merging changes.
java-api-consistency-validator
Validate API consistency between two versions of Java libraries. Use when you need to compare API behavior, signatures, and exceptions between Java library versions to identify breaking changes, incompatible modifications, and behavior differences. The skill performs static analysis of Java code, compares method…
ts-audit
Audit TypeScript and React code against expert-level best practices from 9 TypeScript library references. Use when the user wants to review, audit, check, or improve TypeScript code quality — including requests like "audit this file", "review my types", "check my TypeScript", "what's wrong with this code", "improve my…