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.
npx skills add rafaelandrade74/spec-forge --skill speckit-constitutiongit clone --depth 1 https://github.com/rafaelandrade74/spec-forgeWrote 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.
[](https://agentmods.dev/skills/rafaelandrade74/spec-forge/speckit-constitution)<a href="https://agentmods.dev/skills/rafaelandrade74/spec-forge/speckit-constitution"><img src="https://agentmods.dev/badge/skills/rafaelandrade74/spec-forge/speckit-constitution.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.01701 |
| Opus 5 | $0.00018 | $0.00851 |
| Sonnet 5 | $0.00007 | $0.00340 |
| Haiku 4.5 | $0.00004 | $0.00170 |
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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 139 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).
Scope Guard
This command's own work is limited to updating the project constitution itself. Dependent templates and commands read the constitution at runtime and are not modified here.
- Classify every part of the user input as either constitution content or a separate, non-governance intent.
- If the input includes feature implementation, code generation, refactoring, building, or deployment requests, you MUST NOT execute them. Extract them as deferred intents instead.
- You MUST NOT create, modify, or delete application source files, feature routes, components, tests, deployment files, or other artifacts unrelated to the constitution workflow.
- If it is unclear whether an instruction is constitution content, ask for clarification before making changes.
- After completing the constitution update, include a
Next Actionssection for each deferred intent. List the original intent and suggest the appropriate follow-up Spec Kit command, such as/speckit-specify, without invoking it. - If there are no non-governance intents, omit the
Next Actionssection.
Spec-Forge Setup (replaces file-based Pre-Execution Checks)
This variant persists the constitution in the Spec-Forge database (via its MCP server) instead of
writing .specify/memory/constitution.md. Before anything else:
- Determine the current repository root (absolute path).
- Call the
get_or_create_project_by_repoMCP tool with{ repoPath: <repo root> }. This resolves (or transparently creates) the Spec-Forge project for this repository. Note the returnedprojectId— every subsequent tool call in this command uses it. - Call
get_constitutionwith{ projectId }to load the currently active constitution (if any). This is the "existing document" referenced throughout the Outline below — there is no local file to read.
Outline
You are drafting a new version of the project's constitution, to be persisted via Spec-Forge's
set_constitution tool (not written to a file). The active constitution scaffold is resolved from
the local constitution-template in .specify/templates/constitution-template.md if present in
this repo (this is a static structural template shipped with Spec Kit, not project data, so it is
still read from disk); otherwise draft directly from first principles using the structure below:
Principles, Governance, versioning metadata.
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.
- 7d ago First seen · 139 lines · 36 tokens per session scan A e0f3040e84c7
speckit-constitution is a skill published in the GitHub repository rafaelandrade74/spec-forge (0 stars, last pushed 10d ago), licensed MIT. It adds 36 tokens to every session and 1,701 once invoked, about $0.0002 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-31.
Other skills, from other repositories
artifact-conventions
Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/ / to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-authoring
Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.