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/compozy/skeeper/cy-execute-tasknpx skills add compozy/skeeper --skill cy-execute-taskgit clone --depth 1 https://github.com/compozy/skeeperWhat 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.00080 | $0.00792 |
| Opus 5 | $0.00040 | $0.00396 |
| Sonnet 5 | $0.00016 | $0.00158 |
| Haiku 4.5 | $0.00008 | $0.00079 |
Grade A, and why
cy-execute-task 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 2d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute PRD Task
Execute one PRD task from exploration through tracking updates.
Required Inputs
- Task specification markdown.
- PRD directory path.
- Task file path.
- Master tasks file path.
- Auto-commit mode.
- Optional workflow memory directory path.
- Optional shared workflow memory path.
- Optional current task memory path.
Workflow
-
Ground in repository and PRD context.
- Read the provided task specification.
- Read the repository guidance files named by the caller.
- Read the PRD documents under the provided directory, especially
_techspec.mdand_tasks.md. - Read ADRs from the
adrs/subdirectory of the PRD directory to understand the architectural decision context for this task. - After reading all sources, check for conflicts between the task specification, techspec, and ADRs. If any requirements contradict each other, stop and report the conflict instead of guessing — do not proceed to step 2.
- If the caller provides workflow memory paths, use the installed
cy-workflow-memoryskill before editing code. - Reconcile the current workspace state before new edits.
-
Build the execution checklist.
- Extract deliverables, acceptance criteria, and every explicit
Validation,Test Plan, orTestingitem into a numbered working checklist. - Print the full checklist before starting implementation so it is visible and trackable.
- Capture the concrete pre-change signal that proves the task is not finished yet.
- Use this checklist as a gate: mark each item done as evidence is produced during implementation, and do not proceed to validation until every checklist item has been addressed.
- Extract deliverables, acceptance criteria, and every explicit
-
Implement the task.
- Keep scope tight to the task specification.
- Follow repository patterns and real dependency APIs.
- Record meaningful out-of-scope work as follow-up notes instead of silently expanding the task.
-
Validate and self-review.
- Run every test and validation command listed in the task specification — not just the repository-wide verification.
- Use the installed
cy-final-verifyskill. This step is mandatory regardless of auto-commit mode — always verify before claiming completion. - Perform a self-review after verification and resolve every blocking issue before proceeding.
What ships with it
1 file 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.
- 2d ago First seen · 66 lines · 80 tokens per session scan A 976f78ba1d9a
cy-execute-task is a skill published in the GitHub repository compozy/skeeper (85 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 792 once invoked, about $0.0004 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-30.
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…