ocp: Skill for Claude Code

.claude/skills/speckit-clarify/SKILL.md

speckit-clarify is a skill for Claude Code from dtzp555-max/ocp. It costs 34 tokens per session (3,061 once invoked), scanned A, a copy of speckit-clarify, MIT.

A question-and-answer step for finding missing details in a feature specification. It asks up to five focused questions and records the answers in the specification.

In plain words
What is it for?
Use it when a feature description is incomplete or unclear and the specification needs concrete decisions added. It can also check configured pre-clarification extension hooks.
Why use it?
It reduces ambiguity before planning or coding, so important requirements are not left to guesswork.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

This is dtzp555-max/ocp's own configuration. It tells Claude Code how to work on ocp 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 ocp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dtzp555-max/ocp. 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/dtzp555-max/ocp/main/.claude/skills/speckit-clarify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dtzp555-max/ocp

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 speckit-clarify

README.md
[![agentmods](https://agentmods.dev/badge/skills/dtzp555-max/ocp/speckit-clarify/github.svg)](https://agentmods.dev/skills/dtzp555-max/ocp/speckit-clarify)
Your own site
<a href="https://agentmods.dev/skills/dtzp555-max/ocp/speckit-clarify"><img src="https://agentmods.dev/badge/skills/dtzp555-max/ocp/speckit-clarify/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.

agentmods 80×15 button for speckit-clarify

Your own site · 80×15
<a href="https://agentmods.dev/skills/dtzp555-max/ocp/speckit-clarify"><img src="https://agentmods.dev/badge/skills/dtzp555-max/ocp/speckit-clarify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,061 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 94% copy Near-identical to another mod 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.00034 $0.03061
Opus 5 $0.00017 $0.01530
Sonnet 5 $0.00007 $0.00612
Haiku 4.5 $0.00003 $0.00306

Measured 9d ago against content hash 969ca0b0c181, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

speckit-clarify 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 9d 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.

Origin

This is a copy

94% identical to speckit-clarify — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/speckit-clarify/SKILL.md · 254 lines

How it starts

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

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Pre-Execution Checks

Check for extension hooks (before clarification):

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_clarify key
  • If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
  • Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
  • For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
    • If the hook has no condition field, or it is null/empty, treat the hook as executable
    • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
  • When constructing slash commands from hook command names, replace dots (.) with hyphens (-). For example, speckit.git.commit -> /speckit-git-commit.
  • For each executable hook, output the following based on its optional flag:
    • Optional hook (optional: true):
      ## Extension Hooks
      
      **Optional Pre-Hook**: {extension}
      Command: `/{command}`
      Description: {description}
      
      Prompt: {prompt}
      To execute: `/{command}`
      
    • Mandatory hook (optional: false):
      ## Extension Hooks
      
      **Automatic Pre-Hook**: {extension}
      Executing: `/{command}`
      EXECUTE_COMMAND: {command}
      
      Wait for the result of the hook command before proceeding to the Outline.
      
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Outline

Goal: Detect and reduce ambiguity or missing decision points in the active feature specification and record the clarifications directly in the spec file.

Note: This clarification workflow is expected to run (and be completed) BEFORE invoking /speckit.plan. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.

Read the full file on GitHub · 254 lines

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. 9d ago First seen · 254 lines · 34 tokens per session scan A 969ca0b0c181

Subscribe to this mod's changes

speckit-clarify is a skill published in the GitHub repository dtzp555-max/ocp (107 stars, last pushed 8d ago), licensed MIT. It adds 34 tokens to every session and 3,061 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to speckit-clarify, differing in 21 lines, and is treated as a copy.

Related

Other skills, from other repositories