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 liqiongyu/lenny_skills_plus --skill shipping-productsgit clone --depth 1 https://github.com/liqiongyu/lenny_skills_plusWrote 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/liqiongyu/lenny_skills_plus/shipping-products)<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/shipping-products"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/shipping-products/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/liqiongyu/lenny_skills_plus/shipping-products"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/shipping-products.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.00033 | $0.02108 |
| Opus 5 | $0.00016 | $0.01054 |
| Sonnet 5 | $0.00007 | $0.00422 |
| Haiku 4.5 | $0.00003 | $0.00211 |
Grade A, and why
shipping-products 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipping Products
Scope
Covers
- Turning “we need to ship” into a concrete release plan with owners, dates, and a rollout strategy
- Building a Shipping & Launch Pack that makes the release decision-ready (Go/No-go)
- Shipping in small, frequent increments to improve both speed and stability
- Defining a reusable Product Quality List (PQL) and iterating it based on escapes
- Planning measurement, monitoring, rollback, and post-launch learning
When to use
- “We’re launching / releasing / deploying / going live—make a plan and ship.”
- “Create a go/no-go checklist and rollout plan for this release.”
- “We need to ship faster without breaking trust—set up small-batch shipping.”
- “Write release notes + comms + enablement for an upcoming launch.”
When NOT to use
- You don’t yet agree on the problem or target user (use
problem-definition) - You need to right-size scope to hit a date/appetite (use
scoping-cutting) - You need a decision-ready PRD (use
writing-prds) or build-ready spec/design doc (usewriting-specs-designs) - You’re setting long-term strategy/vision (use
defining-product-vision) or choosing among initiatives (useprioritizing-roadmap) - You need a timeline/milestone plan with stakeholder cadence but are not yet launching (use
managing-timelines) - You need launch marketing copy, positioning, or campaign planning (use
launch-marketing) - You’re running a post-incident review after something went wrong (use
post-mortems-retrospectives)
Inputs
Minimum required
- What you’re shipping (feature/change), target users, and where it will be available (platforms, regions, plans)
- Desired ship date/timebox + constraints (compliance, privacy, brand, uptime windows)
- Success metric(s) + guardrails (trust/safety, performance, reliability, support load)
- Rollout context (flags? staged rollout? beta? migration?) + key dependencies
- Stakeholders + DRI (who decides go/no-go) + who is on point during the launch
What ships with it
13 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.
- eval/eval_config.json 644 B
- eval/SHOWCASE.md 5.0 KB
- eval/with_skill.md 33 KB
- eval/without_skill.md 25 KB
- README.md 1.6 KB
- references/CHECKLISTS.md 2.2 KB
- references/EXAMPLES.md 1.8 KB
- references/INTAKE.md 2.1 KB
- references/RUBRIC.md 2.5 KB
- references/SOURCE_SUMMARY.md 1.5 KB
- references/TEMPLATES.md 3.0 KB
- references/WORKFLOW.md 3.1 KB
- skillpack.json 375 B
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 First seen · 140 lines · 33 tokens per session scan A 2d2c5efaf27d
shipping-products is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (52 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 2,108 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-09-03.
Other skills, from other repositories
atmos-migration
This skill helps you migrate a repository to Atmos. It covers native Terraform, Terraform Workspaces, Terramate, Terragrunt, Makefiles, Justfiles, and Taskfiles. It gives minimum-disruption paths, file-layout options, workspace mapping, task-to-command mapping, generatehcl/script decomposition, and the remote-state…
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-init
Bootstrapping new Atmos projects with atmos init: built-in template catalog, differences from atmos scaffold generate, project record, and update-safe 3-way merge.
atmos-workflows
Workflow automation: native step types, multi-step workflows, parallel/matrix/wait/container/emulator steps, when: conditions (CEL), require/assert preconditions, output steps, retries, dependencies, and cross-component orchestration.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
atmos-imports
Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts.