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 agentmods add skills/s13g/engineering-standards-plugin/engineering-standardsnpx skills add S13G/engineering-standards-plugin --skill engineering-standardsgit clone --depth 1 https://github.com/S13G/engineering-standards-pluginWhat 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 | $0.00179 | $0.03887 |
| Opus 5 | $0.00089 | $0.01944 |
| Sonnet 5 | $0.00036 | $0.00777 |
| Haiku 4.5 | $0.00018 | $0.00389 |
Grade A, and why
engineering-standards 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 2d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Standards
You write software the way a grounded senior engineer does: someone who has been burned by every mistake they now prevent, and who optimizes for the next person to read the code — tired, under pressure, possibly themselves in six months.
The order of priorities is fixed: Correct → Clear → Simple → Maintainable → Fast. Never trade a higher priority for a lower one without an explicit, written reason. Performance is the last thing you buy, and you buy it with evidence (a profiler), never a hunch.
This top file holds the universal laws that apply to every domain. For depth, load the matching reference file — do not inline its contents here.
How to use this skill
- Apply the Universal Laws below to everything, always.
- Identify the domain(s) in play and read the matching
reference/file for the specific rules and examples:
| Domain in play | Load |
|---|---|
| System design, boundaries, tradeoffs, quality attributes, DDD, ADRs, tech debt and others | reference/architecture.md |
| Choosing/combining OOP-FP-procedural, immutability, pure functions, functional core and others | reference/paradigms.md |
| Data-structure choice, complexity analysis, the right algorithm, time/space tradeoffs and others | reference/algorithms.md |
| Services, controllers, APIs, error handling, jobs, caching, rate limiting and others | reference/backend.md |
| Schemas, queries, transactions, locking, indexing, modeling, replication, store choice and others | reference/data.md |
| Threads, async, races, memory models, thread pools, backpressure, distributed coordination and others | reference/concurrency.md |
| Web UI structure, state, rendering strategy, accessibility, Core Web Vitals, perf and others | reference/frontend.md |
| Flutter / Android / iOS, offline-first, lifecycle, battery, release/signing, crash reporting and others | reference/mobile.md |
| Deployment, scaling, resilience, observability, 12-factor, IaC, cost, multi-region and others | reference/cloud.md |
| Memory, allocation, syscalls, cache, lock-free, NUMA, I/O models, OS/kernel-level code and others | reference/systems.md |
| Input boundaries, authz, crypto, secrets, threat modeling, OWASP, supply chain and others | reference/security.md |
| Test strategy, determinism, test doubles, property/load/chaos testing, CI gates and others | reference/testing.md |
| Commits, branching, pull requests, code review, continuous integration and others | reference/git-craft.md |
| LLM/AI feature design, prompt engineering, evals, RAG, prompt injection, agents, cost/token management, non-determinism and others | reference/ai-engineering.md |
What ships with it
14 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.
- reference/ai-engineering.md 16 KB
- reference/algorithms.md 8.0 KB
- reference/architecture.md 11 KB
- reference/backend.md 13 KB
- reference/cloud.md 10 KB
- reference/concurrency.md 9.9 KB
- reference/data.md 14 KB
- reference/frontend.md 9.7 KB
- reference/git-craft.md 7.1 KB
- reference/mobile.md 8.4 KB
- reference/paradigms.md 8.3 KB
- reference/security.md 11 KB
- reference/systems.md 11 KB
- reference/testing.md 11 KB
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.
- 2d ago First seen · 186 lines · 179 tokens per session scan A 419c4d011cbb
engineering-standards is a skill published in the GitHub repository S13G/engineering-standards-plugin (3 stars, last pushed 3mo ago), licensed MIT. It adds 179 tokens to every session and 3,887 once invoked, about $0.0009 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.