ai-platform-engineering: Skill for Claude Code

.claude/skills/speckit.constitution/SKILL.md

speckit.constitution is a skill for Claude Code from caipe-io/ai-platform-engineering. It costs 0 tokens per session (1,332 once invoked), scanned A, original, Apache-2.0.

A workflow for creating or amending a project's constitution: a document that defines its purpose, principles, development rules, and non-negotiable constraints.

In plain words
What is it for?
Use it to create a constitution from a template or update an existing one in response to a specific requested change.
Why use it?
It gives the project a shared set of rules for guiding feature work and architectural decisions.

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 →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is ln -sf ../../docs/plans/CONSTITUTION.md .specify/memory/constitution.md.

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.constitution/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.constitution

README.md
[![agentmods](https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.constitution.svg)](https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.constitution)
Your own site
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.constitution"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.constitution.svg" alt="Measured on agentmods" 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 1,332 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00000 $0.01332
Opus 5 $0.00000 $0.00666
Sonnet 5 $0.00000 $0.00266
Haiku 4.5 $0.00000 $0.00133

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

Security

Grade A, and why

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

.claude/skills/speckit.constitution/SKILL.md · 135 lines

How it starts

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


description: Create or amend the project constitution handoffs:

  • label: Create Feature Spec agent: speckit.specify prompt: Create a spec for...
  • label: Review Architecture agent: speckit.plan prompt: Review architecture alignment with constitution

User Input

$ARGUMENTS

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

Outline

The constitution is the governing document for the project. It defines core principles, development workflow, and governance rules that all agents and engineers must follow. It lives at docs/plans/CONSTITUTION.md and is symlinked from .specify/memory/constitution.md.

Step 1: Determine Mode

Check whether docs/plans/CONSTITUTION.md exists:

  • If it does NOT existCreate mode (go to Step 2)
  • If it existsAmend mode (go to Step 3)

If the user input is empty:

  • In create mode: ask the user to describe the project's purpose, core values, and any non-negotiable constraints
  • In amend mode: ask the user what they want to change and why

Step 2: Create New Constitution

  1. Load the template from templates/constitution-template.md to understand the required structure and sections.

  2. Gather project context:

    • Read README.md (if it exists) for project purpose and scope
    • Read docs/plans/ARCHITECTURE.md (if it exists) for technical context
    • Use the user's input for principles and values
  3. Fill the template by replacing all [PLACEHOLDER] tokens with concrete content derived from the project context and user input:

    • Replace [PROJECT_NAME] with the actual project name
    • Replace each [PRINCIPLE_N_NAME] and [PRINCIPLE_N_DESCRIPTION] with real principles
    • Add or remove principle sections as needed (the template shows 5 examples but the actual count depends on the project)
    • Replace [SECTION_2_NAME], [SECTION_3_NAME] and their content with appropriate sections for the project
    • Fill [GOVERNANCE_RULES] with concrete governance rules
    • Set [CONSTITUTION_VERSION] to 0.0.1, [RATIFICATION_DATE] and [LAST_AMENDED_DATE] to today's date

Read the full file on GitHub · 135 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 · 135 lines · 0 tokens per session scan A 5ece9b3c4a3d

Subscribe to this mod's changes

speckit.constitution is a skill published in the GitHub repository caipe-io/ai-platform-engineering (407 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,332 tokens. 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.