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 agentmods add commands/unbound-force/gaze/uf.constitution-checkgit clone --depth 1 https://github.com/unbound-force/gazeWrote 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/commands/unbound-force/gaze/uf.constitution-check)<a href="https://agentmods.dev/commands/unbound-force/gaze/uf.constitution-check"><img src="https://agentmods.dev/badge/commands/unbound-force/gaze/uf.constitution-check.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.00013 | $0.00691 |
| Opus 5 | $0.00006 | $0.00345 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
uf.constitution-check 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 5d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: /uf.constitution-check
Description
Compares a hero repository's constitution against the Unbound Force org constitution and produces a structured alignment report. The report shows whether each org principle is supported by the hero's principles, identifies contradictions and gaps, and checks for a parent constitution reference.
Usage
/uf.constitution-check [hero-constitution-path] [org-constitution-path]
Arguments
- hero-constitution-path (optional): Path to the hero constitution
file. Defaults to
.specify/memory/constitution.mdin the current repository. - org-constitution-path (optional): Path to the org constitution
file. Defaults to
.specify/memory/constitution.mdin the current repository if it is the unbound-force meta repo.
Examples
# Check the current repo's constitution against the org constitution
/uf.constitution-check
# Check a specific hero constitution
/uf.constitution-check /path/to/hero/.specify/memory/constitution.md
# Check with explicit org constitution path
/uf.constitution-check /path/to/hero/constitution.md /path/to/org/constitution.md
Instructions
-
Parse
$ARGUMENTSto extract optional file paths. -
Locate the org constitution:
- If a second argument is provided, use it as the org constitution path.
- Otherwise, check if the current repository is the unbound-force
meta repo (look for
docs/heroes.mdat the repo root). If so, use.specify/memory/constitution.mdas the org constitution. - If the current repo is NOT the meta repo, look for the org
constitution at
../unbound-force/.specify/memory/constitution.md(sibling directory). If not found, ask the user for the path.
-
Locate the hero constitution:
- If a first argument is provided, use it as the hero constitution path.
- Otherwise, use
.specify/memory/constitution.mdin the current repository. - If the current repo IS the meta repo and no hero path was specified, ask the user which hero to check.
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.
- 5d ago First seen · 86 lines · 13 tokens per session scan A a1e53faa91fc
uf.constitution-check is a command published in the GitHub repository unbound-force/gaze (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 691 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.