skeeper: Skill for Claude Code

.agents/skills/cy-spec-peer-review/SKILL.md

cy-spec-peer-review is a skill for Claude Code from compozy/skeeper. It costs 97 tokens per session (1,402 once invoked), scanned A, original, MIT.

An optional second-opinion review of a technical specification (a written plan for building software) by another AI model. It runs only after the user approves the draft and asks for the review.

In plain words
What is it for?
Reviewing an approved TechSpec, collecting external feedback, and preparing that feedback for possible incorporation.
Why use it?
It helps uncover gaps or questionable decisions before work begins. The findings remain for the user to decide whether to apply.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is compozy/skeeper's own configuration. It tells Claude Code how to work on skeeper itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything skeeper configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/compozy/skeeper/main/.agents/skills/cy-spec-peer-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/compozy/skeeper

Made for: Claude Code.

Wrote 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.

agentmods badge for cy-spec-peer-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/compozy/skeeper/cy-spec-peer-review.svg)](https://agentmods.dev/skills/compozy/skeeper/cy-spec-peer-review)
Your own site
<a href="https://agentmods.dev/skills/compozy/skeeper/cy-spec-peer-review"><img src="https://agentmods.dev/badge/skills/compozy/skeeper/cy-spec-peer-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,402 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00097 $0.01402
Opus 5 $0.00048 $0.00701
Sonnet 5 $0.00019 $0.00280
Haiku 4.5 $0.00010 $0.00140

Measured 8d ago against content hash 04258963fd74, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

cy-spec-peer-review 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 8d 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.

.agents/skills/cy-spec-peer-review/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec Peer Review

Codex authors AGH TechSpecs with gpt-5.4 at reasoning_effort=xhigh; Claude Opus pressure-tests them. This skill runs that pressure-test only when the user explicitly asks for a review round after approving the current draft. It does not auto-run, auto-incorporate findings, or auto-loop additional rounds.

User Decisions

When this skill instructs the agent to ask whether to incorporate findings or run another round, it MUST use the runtime's dedicated interactive question tool — the tool or function that presents a question to the user and pauses execution until the user responds.

If the runtime does not provide such a tool, present the question as the complete assistant message and stop generating. Do not answer the question on the user's behalf.

Required Inputs

  • techspec-path (optional): explicit path to the _techspec.md under review. When omitted, resolve to the most recently modified .compozy/tasks/<slug>/_techspec.md whose sibling _meta.md shows Pending: > 0 or no _meta.md exists yet.

Procedures

Step 1: Validate Input and Context

  1. Resolve techspec-path. If omitted, list candidate paths and pick the freshest.
  2. Confirm the user has already approved the current draft or explicitly asked to review the saved spec as-is.
  3. Read the spec and confirm it is a final-shape TechSpec (has Architectural Boundaries, Implementation Steps, Test Strategy sections) — not a draft.
  4. Read references/quality-markers.md and verify the spec carries the six markers (boundary statement, listed boundaries, Go interface signatures, data-model field rationale, side-table-vs-JSON decisions, lease/safety invariants enumerated). If any marker is missing, abort and report the missing markers — Opus review is wasted on incomplete specs.
  5. Resolve the slug from the path; ensure .compozy/tasks/<slug>/ exists and is writable.
  6. Determine the next review round number by listing existing qa/peer-review-result-round*.json files. Start at round1 when none exist.

Read the full file on GitHub · 84 lines

Files

What ships with it

2 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.

Changes

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.

  1. 8d ago First seen · 84 lines · 97 tokens per session scan A 04258963fd74

Subscribe to this mod's changes

cy-spec-peer-review is a skill published in the GitHub repository compozy/skeeper (85 stars, last pushed 3mo ago), licensed MIT. It adds 97 tokens to every session and 1,402 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens