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/frostney/gocciascript/software-engineering-excellencenpx skills add frostney/GocciaScript --skill software-engineering-excellencegit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/frostney/gocciascript/software-engineering-excellence)<a href="https://agentmods.dev/skills/frostney/gocciascript/software-engineering-excellence"><img src="https://agentmods.dev/badge/skills/frostney/gocciascript/software-engineering-excellence.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.01041 |
| Opus 5 | $0.00031 | $0.00521 |
| Sonnet 5 | $0.00012 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
software-engineering-excellence 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 3d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software engineering excellence
Leave the system more maintainable and the next change easier. Find simple solutions for complex problems, but no shortcuts. Lead with questions that reveal the problem's real shape before selecting implementation mechanics. A better question separates the desired outcome, hard constraints, and observed failure from the mechanism currently being discussed; its answer can change the solution rather than merely select details within it.
Working standard
- Ground in current reality. Read applicable instructions, source, project-defined commands, primary specifications, and durable decisions. Treat issue text, comments, tests, docs, and prior notes as leads until verified. Run the named reproduction or artifact when possible, then act.
- Reuse by meaning. Search for existing helpers, patterns, definitions, and vocabulary. Reuse when semantics match; do not abstract merely similar shapes.
- Solve the complete in-scope problem. Cover real success, failure, and state-transition paths. Fix blockers that invalidate the requested result; report unrelated findings without absorbing them into scope.
- Validate the real bar. Observe every claimed pass, number, behavior, and
action in the current run. Reproduce defects when possible, add meaningful
regression coverage, and run the repository's relevant gate. Never weaken a
gate to obtain green output. When a gate fails, diagnose the failure, using
the registered
diagnosing-bugsskill when available. Report the diagnosis and evidence before changing code. If the failure blocks the requested result or belongs to its authorized scope, fix it and verify the fix; otherwise report it to the user without absorbing it into the current change. - Make every surface earn its cost. Add only code, tests, fallbacks, abstractions, or tools with a real caller, requirement, or failure mode. Remove unused surfaces.
- Respect authority boundaries. Diagnosis, review, and planning authorize assessment; change requests authorize reversible in-scope implementation and relevant validation. Pause only for a material product, architecture, security, compatibility, or scope choice that evidence cannot resolve.
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.
- 3d ago First seen · 100 lines · 62 tokens per session scan A 40a4675f2bea
software-engineering-excellence is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed 7d ago), licensed MIT. It adds 62 tokens to every session and 1,041 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
qcad
Use when editing DXF files with a professional open-source 2D CAD application — CAM output, part libraries, isometric projection. QCAD: open-source 2D CAD with DXF as native format, scriptable via ECMAScript.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
git-step-commit
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
manage-prd-docs
Automatically manage product requirements across current decisions in docs/PRD.md and docs/prd/, mature future plans under docs/plans/, and active implementation under docs/work/. Use whenever the conversation discusses, clarifies, versions, plans, implements, completes, splits, or migrates a product requirement or…
modernize-ecmascript
当 Agent 编写或修改 JavaScript、TypeScript，用户要求按指定环境、输出版本、ES20xx 或具体语法编写代码，询问某项 ECMAScript 语法、标准内置 API 或提案能否采用，或者要求审查仓库中可简化、可现代化的写法时，应使用本 Skill。围绕目标文件真实经过的解析器、转换器和输出目标判断新语法能否安全采用，并按需读取 TC39 Atlas 的提案阶段、官方仓库、polyfill 与实现线索。.
codebase-audit
Audits the current repository for systemic correctness, architecture, churn, simplification, clarity, test value, and operational risks using current source and reproducible probes. It can delegate evidence gathering across bounded capability and perspective lanes. Use when the user runs /codebase-audit or asks for an…