Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add int2t05/engineering-skills/plugin install engineering-skillsWrote 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/int2t05/engineering-skills/skill-authoring)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/skill-authoring"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/skill-authoring.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.1 | $0.00118 | $0.01973 |
| Opus 5 | $0.00059 | $0.00986 |
| Sonnet 5 | $0.00024 | $0.00395 |
| Haiku 4.5 | $0.00012 | $0.00197 |
Grade A, and why
skill-authoring 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 6d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Authoring
Create, edit, and evaluate skills in this collection. Every skill conforms to the anatomy in
references/skill-anatomy.md and passes scripts/validate-skills.sh. This skill is the authoring
half — using-skills routes work to existing skills; this one makes new ones or fixes existing ones.
When to use
- Creating a new skill (new SDLC phase gap, repeated task worth a skill)
- Editing an existing skill's frontmatter, steps, or references
- Tuning a skill's description triggers (false positives, false negatives, collision with another skill)
- Evaluating a skill — does it fire when it should, stay distinct from neighbors, change agent behavior?
- Triggers on "write a skill", "edit skill", "skill eval", "tune triggers", "写技能", "改技能", "技能评估"
Not for: routing a task to an existing skill (use using-skills); designing an MCP server (out of scope, see official mcp-builder docs); writing project docs like PRD/README (use spec/oss-polish).
Steps
1. Check the anatomy before writing
Load ${CLAUDE_PLUGIN_ROOT}/references/skill-anatomy.md — the folder layout, frontmatter rules (name + description + optional disable-model-invocation only), the four body sections (When to use / Steps / Verify / References), the **Output:** convention, progressive disclosure (15-150 line SKILL.md, depth in references/), and the description hybrid format (Use when… + Triggers on… + exclusions, ≤1024 chars, no cross-skill phrase collisions).
2. Place the skill and wire the backbone
- Phase — pick the phase by output type + consumer, not by method. A skill producing a design artifact for design consumers goes in 03-design even if it reuses research methods (see
design-research). Method does not set phase; output and consumers do. - Backbone — every skill links
engineering-principles.md. PM-side skills also linkproduct-principles.md; UIUX skills also linkdesign-principles.md. The validator enforces these (seescripts/validate-skills.shpm_skills/uiux_skillslists — add the new skill there if it's PM or UIUX). - Path —
skills/<phase>/<name>/SKILL.md(kebab-case name, uppercase SKILL.md).
What ships with it
2 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.
- 6d ago First seen · 94 lines · 118 tokens per session scan A a50cac6c9f89
skill-authoring is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 6d ago), licensed MIT. It adds 118 tokens to every session and 1,973 once invoked, about $0.0006 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
pr-workflow
Crear pull requests completas con descripcion, labels y reviewers.
sonarqube
Levantar SonarQube con Docker, analizar el código y proponer mejoras. También: análisis estático, deuda técnica, code smells, cobertura, calidad automatizada.
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review.
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
second-pass-review
Independent audit of sanitized specs in workspace/output/. Three parallel LLM-based reviewer roles check structural leakage, content contamination, and behavioral completeness. Run AFTER Layer 5 sanitization, BEFORE implementation handoff.