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/shipping)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/shipping"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/shipping.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.00048 | $0.01688 |
| Opus 5 | $0.00024 | $0.00844 |
| Sonnet 5 | $0.00010 | $0.00338 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
shipping 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipping and Launch
Ship with confidence: deploy safely, with monitoring in place, a rollback plan ready, and a clear definition of success. Every launch should be reversible, observable, and incremental. Faster is safer — smaller batches and more frequent releases reduce risk, not increase it.
When to use
- Deploying a feature or significant change to production for the first time.
- Migrating data or infrastructure.
- Opening a beta or early access program.
- Any deployment that carries risk (all of them).
Not for: setting up CI/CD pipelines (use ci-cd); routine commits, branching, or conflict resolution (use git-workflow); rolling back a live failure (use debugging first, then ship the fix).
Steps
1. Complete the pre-launch checklist
Before deploying, every section must be green.
Code quality
- All tests pass (unit, integration, e2e)
- Build succeeds; lint and type checking pass
- Code reviewed and approved
- No
console.log/ debug statements; no pre-launch TODOs left - Error handling covers expected failure modes
Security
- No secrets in code or version control
- Dependency audit (
npm audit,pip-audit,cargo audit, ...) shows no critical/high vulnerabilities - Input validation on all user-facing endpoints
- Authn/authz in place; rate limiting on auth endpoints
- Security headers (CSP, HSTS); CORS scoped to specific origins, not wildcard
Performance & accessibility — adapt to your service type. The checklist below assumes a web frontend; for a backend service focus on p99 latency, error rate, and connection-pool saturation; for a CLI/library focus on startup time, binary size, and cross-platform tests.
- Core Web Vitals in "Good" thresholds; bundle within budget
- Images optimized (compression, responsive sizes, lazy loading)
- No N+1 queries on critical paths; indexes and caching in place
- Caching configured for static assets and repeated queries
- Keyboard navigation, screen reader, WCAG 2.1 AA contrast
- Focus management for modals and dynamic content
- Descriptive error messages associated with form fields
- No axe-core / Lighthouse accessibility warnings
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.
- 6d ago First seen · 138 lines · 48 tokens per session scan A 0af6da8ccbdc
shipping is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 1,688 once invoked, about $0.0002 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
phx-review
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
pr-workflow
Crear pull requests completas con descripcion, labels y reviewers.
plugin-dev
Validate plugin SKILL.md frontmatter and audit hook scripts for silent failures. Run validation to check all plugins pass schema, source path, and frontmatter checks. Run hook audit to detect unhandled errors in shell and Python scripts.
content-audit
Content file quality audit across 8 dimensions (CC1-CC8): encoding artifacts (NBSP, mojibake, zero-width), markdown syntax (broken italic, orphan backslash), CMS migration artifacts (Joomla/WordPress/PHP), frontmatter quality, image integrity, link integrity with anchor validation, content completeness, and…
modernize
Survey a project for ways to adopt newer language and major-dependency features that did not exist when the code was written, replacing boilerplate with modern idioms. Use when the user wants to modernize a codebase, adopt new language features, retire dependencies the stdlib now subsumes, or catch a project up to…
fec-refactor-clean
A safe cleanup workflow for unused front-end code, exports, routes, components, and dependencies.