Borrowing it
Nothing to install: this file belongs to compozy/skeeper. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/compozy/skeeper/main/.agents/skills/cy-execute-task/SKILL.mdgit clone --depth 1 https://github.com/compozy/skeeperWrote 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/compozy/skeeper/cy-execute-task)<a href="https://agentmods.dev/skills/compozy/skeeper/cy-execute-task"><img src="https://agentmods.dev/badge/skills/compozy/skeeper/cy-execute-task/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/compozy/skeeper/cy-execute-task"><img src="https://agentmods.dev/badge/skills/compozy/skeeper/cy-execute-task.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.00080 | $0.00792 |
| Opus 5.5 | $0.00032 | $0.00317 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (89 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 792 once invoked, about $0.0003 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…