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-bumpnpx skills add cozystack/ccp --skill package-bumpgit 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.00185 | $0.13995 |
| Opus 5 | $0.00093 | $0.06998 |
| Sonnet 5 | $0.00037 | $0.02799 |
| Haiku 4.5 | $0.00018 | $0.01400 |
Grade E, and why
package-bump scanned grade E with 3 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
If the user picks a different context, record their choice into `$KUBE_CONTEXT` and pass `--context $KUBE_CONTEXT` to every subsequent `kubectl` / `cozyhr` call. **Never** call `kubectl config use-context` — switching th Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
3. Run `make --directory $PKG_DIR update`. The target's pre-clean (`rm -rf charts/`) is preserved by editing the version literal only. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. **Tools installed**: check that `yq` (v4 mikefarah), `jq`, `helm`, `docker buildx`, `cozyhr`, `cozyvalues-gen`, `kubectl`, `git`, `gh` are on `PATH` via `command -v`. Missing required tools → print install hints (link How it starts
The opening of the file, as written. The whole thing — 724 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cozystack:package-bump
This skill bumps the upstream version of a single package inside the cozystack monorepo (~/git/github.com/cozystack/cozystack, layout packages/{apps,system,extra,core}/<name>/). The bump is treated as a real review task — the changelog between the current and target versions is read, breaking changes and deprecations are surfaced, the package's own values.yaml and templates are adapted accordingly, and the result is verified locally before any commit.
This skill does modify files inside the cozystack checkout, does create one signed-off commit, and may deploy the bumped version to a dev cluster on user approval. It does not push, open PRs, or touch production clusters.
Work in reasoning mode. Follow the phases in order. When a step fails or is ambiguous, stop and ask — do not guess upstream versions, image digests, or breaking-change semantics. Use the phrasing "cozystack:package-bump" (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, commit messages, and PR body drafts stay in their canonical form (usually English) per cozystack's public-content rules.
Phase 1 — Parse arguments
$ARGUMENTS contains the free-form tail after /cozystack:package-bump. Extract:
- Positional
<package-path-or-name>— required. Either an absolute path, a path relative to the monorepo root (packages/apps/postgres), or a bare name (postgres) resolved againstpackages/{apps,system,extra,core}/<name>/. If multiple matches are found across types, ask the user viaAskUserQuestionwhich one.packages/library/andpackages/tests/are explicitly out of scope — those are internal helpers without an upstream version to track. If a bare-name match falls only into one of those, stop and explain. --target-version=<ver>— explicit target (16.4,v1.25.0,2.7.5). If omitted, Phase 3 resolves the latest from upstream and asks the user to confirm.--no-deploy— skip Phase 9 entirely (no prompt, no deploy).--registry=ttl.sh/<uuid>— reuse an existingttl.shregistry from a previous run (so a rebuild lands on the same image path). If omitted, Phase 9 generates a fresh UUID.--allow-dirty— let Phase 2 proceed when the working tree has uncommitted changes. Default is to refuse.
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 · 724 lines · 185 tokens per session scan E 0e5dc3e25d02
package-bump is a skill published in the GitHub repository cozystack/ccp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 185 tokens to every session and 13,995 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it E with 3 findings (reaches for credential files, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…