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 Neeeophytee/agent-stylebooks --skill sec-plain-englishgit clone --depth 1 https://github.com/Neeeophytee/agent-stylebooksWrote 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/neeeophytee/agent-stylebooks/sec-plain-english)<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/sec-plain-english"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/sec-plain-english/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/neeeophytee/agent-stylebooks/sec-plain-english"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/sec-plain-english.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.00067 | $0.00802 |
| Opus 5 | $0.00034 | $0.00401 |
| Sonnet 5 | $0.00013 | $0.00160 |
| Haiku 4.5 | $0.00007 | $0.00080 |
Grade A, and why
sec-plain-english 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 11d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEC plain English
Make material information understandable to an investor without changing the legal or economic substance. This skill is a writing aid, not legal or securities-law compliance advice.
Lock the disclosure record
- Inventory every material fact, number, defined term, condition, exception, cross-reference, risk, and forward-looking qualification before rewriting.
- Preserve the scope and strength of
may,could,expect,believe,subject to, and similar language. Never convert a conditional statement into a certainty. - Do not add a legal conclusion, safe-harbor claim, performance promise, or compliance claim.
- Keep required legends and mandated wording unchanged unless securities counsel authorizes revision. Flag conflicts between clarity and required language.
- Require legal and subject-matter review before filing or distributing regulated disclosure.
Design for the investor's decision
- Identify the intended investor and the decision the document supports.
- Put material, issuer-specific information before process history and boilerplate.
- State the transaction, security, price or valuation basis, use of proceeds, dilution, conflicts, and principal risks where applicable and supported.
- Group related facts so the reader does not have to join a claim to a distant exception.
- Move detail only when the summary remains fair and the full qualification is easy to find.
Explain risks as relationships
- Name the condition or cause, the event that may occur, and the consequence for the investor or issuer.
- State who or what is exposed, the relevant time horizon, and any concentration or dependency.
- Distinguish a current circumstance from a hypothetical future risk.
- Keep mitigating factors separate and proportionate; do not use them to cancel the risk.
- Remove generic risk language only when counsel confirms that no material meaning is lost.
- Do not rank or label a risk as likely, remote, severe, or immaterial without support.
What ships with it
3 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.
- 11d ago First seen · 74 lines · 67 tokens per session scan A 859b89b715ad
sec-plain-english is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (60 stars, last pushed 19d ago), licensed MIT. It adds 67 tokens to every session and 802 once invoked, about $0.0003 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
lov-review-doc
A contract review assistant for agreements such as NDAs, service contracts, data agreements, employment contracts, licences, and investment documents. It can analyse risks, add comments, and suggest revised wording.
lov-china-website-filing
A workflow for preparing and launching websites in mainland China, including ICP filing and public-security filing. ICP filing is the registration required for many mainland websites, while public-security filing is a separate police registration.
contract-review-pro
Professional-grade contract review skill that adds comment-based issue annotations without changing original text. Enforces a four-layer review (entity verification, basic, business, legal), writes structured comments (issue type, risk reason, revision suggestion) with risk level encoded via reviewer name, and…
extendr-bindings
extendr conventions for exposing a Rust core to R: extendr macros and module registration, Robj type mapping, NA handling, rextendr builds, R package scaffolding, and CRAN compliance. Load when generating or reviewing extendr R bindings for a Rust library.
r-conventions
R code conventions covering R 4.1+, tidyverse/base style, styler/lintr, roxygen2, testthat, error handling, input validation, C/C++/Rust interop, and CRAN compliance. Load when writing or reviewing R code.
lov-legal-pages
A website content tool that drafts privacy policy and terms-of-service pages from the project’s real business and data-handling facts. These pages explain how a service uses information and what rules apply to its users.