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 r13v/pi-feature-dev --skill stegit clone --depth 1 https://github.com/r13v/pi-feature-devWrote 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/r13v/pi-feature-dev/ste)<a href="https://agentmods.dev/skills/r13v/pi-feature-dev/ste"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/ste/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/r13v/pi-feature-dev/ste"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/ste.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.00039 | $0.01714 |
| Opus 5.5 | $0.00016 | $0.00686 |
| Sonnet 5.5 | $0.00008 | $0.00343 |
| Haiku 4.5 | $0.00004 | $0.00171 |
Grade A, and why
ste 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STE
Write English that has one clear meaning and a structure that is easy to parse. Preserve technical accuracy before you simplify language.
Select the Operating Mode
Use strict STE mode when the user requests ASD-STE100 compliance or works on regulated, maintenance, operational, or safety-critical documentation.
- Apply Issue 9 rules and the applicable project directives.
- Verify general vocabulary against the official Issue 9 dictionary.
- Verify technical nouns and verbs against the project glossary.
- Use
STE-aligned draftwhen these lexical checks are not possible.
Use STE clarity mode for prompts, tool descriptions, error messages, agent instructions, status reports, translation-ready text, and other technical or operational English.
- Transfer the clarity rules that fit the text.
- Prefer explicit actors, actions, conditions, inputs, and results.
- Do not imply formal ASD-STE100 compliance.
Load References Selectively
- Read references/writing-rules.md for strict STE work, compliance reviews, safety text, word-count decisions, or rule details.
- Read references/checklist.md for strict reviews, audits, high-risk text, or long documents. Use its quick check or full check as the task requires.
- Read references/use-cases.md when the text type needs a clear information order or a reusable structure.
- Read references/before-after.md when rewriting dense text, explaining changes, or producing a comparison.
- Read all user-supplied glossaries, safety policies, style guides, and regulatory directives that apply.
If sources conflict, follow the explicit regulatory or project requirement and report the deviation. Do not merge inconsistent terminology.
Preserve Meaning
Before rewriting:
- Identify each fact, action, condition, limit, unit, exception, warning, causal relation, and cross-reference.
- Resolve what each pronoun and modifier refers to.
- Keep the original sequence and scope unless the user authorizes a technical change.
- Ask when ambiguity can change safety, responsibility, or task outcome.
What ships with it
6 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.
- 9d ago Changed · +36 lines 06baea34dbbf
- 18d ago Changed · +2 lines abf1c63a495e
- 1mo ago Changed · +4 lines 5999e806433e
- 1mo ago Changed · +3 lines · -90 tokens per session cce1f43fbf89
- 2mo ago First seen · 149 lines · 129 tokens per session scan A 8978a3fb536d
ste is a skill published in the GitHub repository r13v/pi-feature-dev (3 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 1,714 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…