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/cozystack/ccp/package-deploynpx skills add cozystack/ccp --skill package-deploygit clone --depth 1 https://github.com/cozystack/ccpWhat 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.00099 | $0.03377 |
| Opus 5 | $0.00049 | $0.01688 |
| Sonnet 5 | $0.00020 | $0.00675 |
| Haiku 4.5 | $0.00010 | $0.00338 |
Grade A, and why
package-deploy 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 yesterday.
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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cozystack:package-deploy
This skill deploys a single Cozystack package (packages/system/<pkg> or packages/apps/<pkg>) from the current checkout to a Kubernetes cluster, using the repo's own make targets and the cozyhr wrapper. It is designed for developer iteration against a dev cluster — do not run it against production. Touching a real cluster requires explicit confirmation at a gate below.
Work in reasoning mode. Follow the phases in order. Skip steps only when the argument flags explicitly say so. When a step fails, stop and report — do not try to work around by disabling safety checks.
Use the phrasing "cozystack:package-deploy" (not "the skill") in messages to the user, and state progress at each phase boundary.
Match the operator's natural language detected from prior conversation messages — use it in prompts, AskUserQuestion options, summaries, and gates. Code identifiers, commands, file paths, and commit messages stay in their canonical form (usually English).
Phase 1 — Parse arguments
$ARGUMENTS contains the free-form tail after /cozystack:package-deploy. Extract:
- Positional
<package>— the directory name underpackages/system/orpackages/apps/. Required. --registry=<reg>— container registry to push to (e.g.,ghcr.io/<your-username>or your team registry). If unset, fall back to a privatettl.sh/<uuid>path (Phase 4).--tag=<tag>— image tag. Default:latest(sinceTAGinhack/common-envs.mkresolves tolatestoutside of a git tag).--context=<ctx>—kubectlcontext to target. Default: whateverkubectl config current-contextreturns (with confirmation in Phase 3).--namespace=<ns>— Kubernetes namespace. Default: value ofNAMESPACEin the packageMakefile.--release=<name>— Helm release name. Default: value ofNAMEin the packageMakefile.--skip-build— skipmake image; use whatever image digest is already invalues.yaml.--no-resume— after deploy, do not prompt to resume the suspended HelmRelease. Useful for leaving the cluster on the custom build while iterating further.--keep-values— do not revertpackages/…/values.yamlat the end. Useful if the user wants to inspect whatmake imagewrote.
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.
- yesterday First seen · 239 lines · 99 tokens per session scan A d9fb0dd2c89f
package-deploy is a skill published in the GitHub repository cozystack/ccp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 99 tokens to every session and 3,377 once invoked, about $0.0005 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
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
amazon-bestseller-listing
Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
cabloy-worktree-environment
This skill must be used only when the user explicitly invokes /cabloy-worktree-environment or explicitly asks to perform the named Cabloy worktree-environment setup. It prepares a confirmation-gated, worktree-local Vona and Zova runtime environment for a linked Cabloy Basic or Cabloy Start Git worktree using Git…
shopify-hydrogen
Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager…