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 tmusser/ai-engineering-skills --skill constitution-litegit clone --depth 1 https://github.com/tmusser/ai-engineering-skillsWrote 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/tmusser/ai-engineering-skills/constitution-lite)<a href="https://agentmods.dev/skills/tmusser/ai-engineering-skills/constitution-lite"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/constitution-lite/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.
<a href="https://agentmods.dev/skills/tmusser/ai-engineering-skills/constitution-lite"><img src="https://agentmods.dev/badge/skills/tmusser/ai-engineering-skills/constitution-lite.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.00819 |
| Opus 5 | $0.00019 | $0.00409 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade C, and why
constitution-lite scanned grade C with 1 finding 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.
Instruction-override phrasinghighPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
`CONSTITUTION.md` is a workflow artifact. It does not override system instructions, How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constitution Lite
Purpose
Record only the durable rules that constrain what an agent may decide or do across multiple tasks. This is an authority boundary, not a project handbook.
Project instructions are not constitution rules. Architecture notes, repo layout,
commands, coding style, naming conventions, framework choices, and ordinary team
preferences belong in native project instructions such as CLAUDE.md or AGENTS.md.
Task-specific requirements belong in SPEC.md, scope-freeze, or SHIP.md.
When to use
Use when repeated, delegated, scheduled, or autonomous work needs a small set of stable constraints that should survive across tasks, such as:
- human approval before destructive or external side effects
- protected production, data, credential, or customer boundaries
- tests or evidence that an agent may not weaken to make work pass
- decisions an agent is never authorized to make alone
Skip this skill when the need is only project onboarding, commands, architecture, style, a temporary implementation constraint, or one task's acceptance criteria.
Inputs
- Existing
CLAUDE.md,AGENTS.md, or equivalent project instructions if present - Stable risk and authority boundaries
- Protected resources, environments, data, or interfaces
- Human approval requirements
- Existing task or shipping controls that should not be duplicated
Workflow
- Read existing project instructions first. Do not copy their conventions into the constitution.
- List candidate cross-task rules.
- Keep a candidate only when violating it should require a human decision, explicit review, or a hard stop across more than one task.
- Classify each retained rule as
MUST,MUST NOT, orHUMAN GATE. - Make each rule observable where possible: name the protected resource, forbidden action, approval event, or evidence requirement.
- Remove architecture preferences, commands, style guidance, framework choices, and task-local constraints.
- If the constitution conflicts with live project instructions or a task contract, stop and ask for a human decision. Do not silently choose an authority winner.
- Name who may amend the constitution and how the amendment is approved.
- Keep the artifact short enough to scan before delegated work.
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.
- 9d ago First seen · 96 lines · 38 tokens per session scan C b8ba2475926d
constitution-lite is a skill published in the GitHub repository tmusser/ai-engineering-skills (4 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 819 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
awsl
Run Claude Code JavaScript Workflows through the awsl compatibility runtime. Use when an agent's current task or loaded Skill requires dispatching a Claude Code Workflow but the host cannot execute that Workflow natively, or when awsl workflow inspection, durable run state, resume, or provider diagnostics are needed.
dwi-all-in-one
Apply the relevant Dwi lenses together when several observed workflow problems co-occur. Select only the lenses the task needs, preserve a silent fast path for clear reversible work, and keep authority and evidence explicit. Prefer a focused module when one issue dominates.
dwi-arc
Structure genuinely multi-agent coding work into bounded cells with one writer per scope, explicit integration, and independent review. Use when several disjoint workstreams justify coordination. Do not use for small tasks, overlapping writers, speculative agent fleets, or process artifacts without demonstrated value.
dwi-bridge
Coordinate bounded work between native Claude and Codex workflows with explicit authority, scope, and evidence. Use for read-only consultation or explicitly authorized execution delegation. Do not create a new connector, share secrets, treat messages as authorization, or allow recursive delegation.
dwi-budget
Set and report practical token, context, time, tool-call, and coordination boundaries for coding-agent work. Use when resource use is unclear or needs a checkpoint. Do not invent measurements, monetary savings, cache benefit, or precision that the harness does not expose.
dwi-evidence
Label coding-agent claims by evidence status, preserve provenance and failures, and separate static, runtime, and human proof. Use before completion, comparison, promotion, or handoff. Do not upgrade observations into guarantees or fabricate missing measurements and approvals.