SuperPlane is an open-source automation system that turns selected software backlog issues into pull requests by coordinating coding agents, source control, testing, review, and approvals. Engineering teams use it to automate routine development work while keeping ambiguous decisions for humans, and the catalogue add-ons support its workflows.
Borrowing it
Nothing to install: this file belongs to superplanehq/superplane. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/superplanehq/superplane/main/.agents/skills/simplified-technical-english/SKILL.mdgit clone --depth 1 https://github.com/superplanehq/superplaneWrote 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/superplanehq/superplane/simplified-technical-english)<a href="https://agentmods.dev/skills/superplanehq/superplane/simplified-technical-english"><img src="https://agentmods.dev/badge/skills/superplanehq/superplane/simplified-technical-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/superplanehq/superplane/simplified-technical-english"><img src="https://agentmods.dev/badge/skills/superplanehq/superplane/simplified-technical-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.00062 | $0.01345 |
| Opus 5 | $0.00031 | $0.00673 |
| Sonnet 5 | $0.00012 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
simplified-technical-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 9d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplified Technical English (ASD-STE100)
Write clear, unambiguous technical English. Prefer STE writing rules over clever or idiomatic phrasing.
This skill applies STE writing rules (grammar and style). It does not embed the copyrighted STE dictionary (~900 approved words). Use simple words with one clear meaning; use SuperPlane technical nouns/verbs for product terms. For full dictionary compliance, consult the official standard: ASD-STE100.
Source: ASD-STE100 Issue 9 (January 2025), Standard for technical documentation. ASD owns the STE trademark and standard; this skill is an operational distillation for agents, not a substitute for the official document.
When this applies
| Text | STE mode |
|---|---|
| PR description Summary and Test plan | Descriptive + procedural |
| Commit message body | Descriptive |
| UI labels, buttons, helper text, empty states, errors, confirmations | Procedural / short descriptive |
| Docs, runbooks, onboarding steps | Procedural and/or descriptive |
Exceptions (do not rewrite these into STE):
- Conventional Commits type prefixes (
feat:,fix:, …) - Code identifiers, API paths, proto names, log lines, and quoted error codes
- Proper nouns and product names (
SuperPlane,GitHub,PostgreSQL) - Issue IDs and DCO trailers
Core rules (must follow)
Words
- Prefer plain words with one meaning. Do not use synonyms for the same idea
in the same surface (
startvsbeginvsinitiate— pick one and keep it). - Keep one technical noun per concept. Use SuperPlane vocabulary
consistently:
canvas,organization,integration,component,trigger,run,approval,console. Spell the product SuperPlane. - Do not use slang, idioms, humor, or jargon that the reader cannot act on.
- Use American English spelling.
- Prefer verbs for actions. Do not hide actions in nouns
(
Create a connection, notPerform connection creation). - Keep multi-word technical nouns to three words or fewer when you invent
a phrase (
deploy approval step, notproduction deploy approval workflow step).
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.
- 9d ago First seen · 151 lines · 62 tokens per session scan A 760a03e644fc
simplified-technical-english is a skill published in the GitHub repository superplanehq/superplane (6,110 stars, last pushed today), licensed Apache-2.0. It adds 62 tokens to every session and 1,345 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
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…
twin-pr-triage
Scan open pull requests, assess risk and complexity, and build a prioritized review queue. Used by digital twin personas to reduce PR review cognitive load.
prettier-docs
Prettier 3.9.5 — opinionated code formatter. CLI, API, config, plugins, editor integration, CI.
cflx-proposal
Create implementation-ready Conflux proposals, including fail-closed visual contracts for UI changes. Use for any request to create, draft, review, or strengthen a proposal or product change.