speckit.constitution

speckit.constitution is an agent for coding agents from mick-gsk/drift. It costs 21 tokens per session (1,764 once invoked), scanned A, a copy of speckit.constitution, MIT.

An agent that creates or updates a project constitution from stated principles. It can also keep related specification templates aligned and check configured pre-update hooks.

In plain words
What is it for?
It is for establishing project rules, revising those rules from user input, and checking extension steps before the constitution changes.
Why use it?
It provides a central set of project principles and reduces the risk that supporting templates become inconsistent.

Agent

Part of the drift plugin — 31 skills, 17 agents shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/mick-gsk/drift/speckit.constitution
Clone the repo
git clone --depth 1 https://github.com/mick-gsk/drift

Or install drift, the plugin that ships this one along with the rest of its 31 skills, 17 agents.

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/agents/mick-gsk/drift/speckit.constitution.svg)](https://agentmods.dev/agents/mick-gsk/drift/speckit.constitution)
Your own site
<a href="https://agentmods.dev/agents/mick-gsk/drift/speckit.constitution"><img src="https://agentmods.dev/badge/agents/mick-gsk/drift/speckit.constitution.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,764 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% 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 $0.00021 $0.01764
Opus 5 $0.00010 $0.00882
Sonnet 5 $0.00004 $0.00353
Haiku 4.5 $0.00002 $0.00176

Measured 4d ago against content hash 58d35eb026f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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

100% identical to speckit.constitution — 0 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.

.github/agents/speckit.constitution.agent.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 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 constitution update):

  • Check if .specify/extensions.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_constitution 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
  • 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

You are updating the project constitution at .specify/memory/constitution.md. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. [PROJECT_NAME], [PRINCIPLE_1_NAME]). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.

Note: If .specify/memory/constitution.md does not exist yet, it should have been initialized from .specify/templates/constitution-template.md during project setup. If it's missing, copy the template first.

Read the full file on GitHub · 151 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. 4d ago First seen · 151 lines · 21 tokens per session scan A 58d35eb026f5

Subscribe to this mod's changes

speckit.constitution is an agent published in the GitHub repository mick-gsk/drift (14 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,764 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to speckit.constitution, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

heal-loop

You are a self-healing fix agent for contract violations. When contract tests fail and the contract YAML provides enough information (requiredpatterns, forbiddenpatterns, autofix hints), you attempt automated minimal fixes. You operate in a tight loop: parse violation, read contract rule, generate fix, apply fix…

Hulupeep/Specflow · 0 tokens

WORKFLOW

These agents make Specflow work with Claude Code as the orchestrator. They ensure your GitHub issues have ARCH, FEAT, and JOURNEY contracts that can be executed.

Hulupeep/Specflow · 0 tokens

team-names

Agent Teams mode assigns mythic Irish names to agents instead of functional IDs like "issue-50". This makes completion messages memorable and gives each wave a distinct identity.

Hulupeep/Specflow · 0 tokens

test-runner

You are a test execution specialist. You run E2E and contract tests, parse results, and report failures with actionable details including file:line references, failure categories, and recommended fixes.

Hulupeep/Specflow · 0 tokens

edge-function-builder

You are a Supabase Edge Function developer for your project. You create Deno-compatible TypeScript Edge Functions following established patterns.

Hulupeep/Specflow · 0 tokens

specflow-uplifter

You are a specflow remediation specialist. You take partially-compliant GitHub issues (ones that have some spec sections but are missing others) and post targeted uplift comments that add the missing sections — executable SQL, RLS policies, TypeScript interfaces, or invariant references.

Hulupeep/Specflow · 0 tokens