ai-platform-engineering: Skill for Claude Code

.claude/skills/speckit.implement/SKILL.md

speckit.implement is a skill for Claude Code from caipe-io/ai-platform-engineering. It costs 0 tokens per session (2,700 once invoked), scanned A, a copy of speckit-implement, Apache-2.0.

A coding-task executor that reads a repository's prepared task list and produces source-code changes and tests. It also checks configured pre-implementation hooks before starting.

In plain words
What is it for?
Use it to implement tasks from a feature plan, run the required prerequisite checks, inspect applicable hooks, and create the related code and tests.
Why use it?
It provides a defined starting process for implementation and makes sure required project checks or extension steps are considered first.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is caipe-io/ai-platform-engineering's own configuration. It tells Claude Code how to work on ai-platform-engineering 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 ai-platform-engineering configures →

Reuse

Borrowing it

Nothing to install: this file belongs to caipe-io/ai-platform-engineering. 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/caipe-io/ai-platform-engineering/main/.claude/skills/speckit.implement/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/caipe-io/ai-platform-engineering

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.implement/github.svg)](https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.implement)
Your own site
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.implement"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.implement/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.implement

Your own site · 80×15
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.implement"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,700 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 88% 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.00000 $0.02700
Opus 5.5 $0.00000 $0.01080
Sonnet 5.5 $0.00000 $0.00540
Haiku 4.5 $0.00000 $0.00270

Measured 1mo ago against content hash 0422b930d09e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speckit.implement 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.

Origin

This is a copy

88% identical to speckit-implement — 27 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.implement/SKILL.md · 207 lines

How it starts

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


description: Execute tasks to produce source code and tests scripts: sh: scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks ps: scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks

User Input

$ARGUMENTS

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

Pre-Execution Checks

Check for extension hooks (before implementation):

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_implement key
  • If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
  • Filter to only hooks where enabled: true
  • 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
  • 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

  1. Run {SCRIPT} from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

Read the full file on GitHub · 207 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. 1mo ago First seen · 207 lines · 0 tokens per session scan A 0422b930d09e

Subscribe to this mod's changes

speckit.implement is a skill published in the GitHub repository caipe-io/ai-platform-engineering (429 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,700 tokens. A static security scan graded it A with 0 findings. It is 88% identical to speckit-implement, differing in 27 lines, and is treated as a copy.