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 zachjxyz/jvn --skill constitution-referencegit clone --depth 1 https://github.com/zachjxyz/jvnWrote 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/zachjxyz/jvn/constitution-reference)<a href="https://agentmods.dev/skills/zachjxyz/jvn/constitution-reference"><img src="https://agentmods.dev/badge/skills/zachjxyz/jvn/constitution-reference/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/zachjxyz/jvn/constitution-reference"><img src="https://agentmods.dev/badge/skills/zachjxyz/jvn/constitution-reference.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.00013 | $0.00224 |
| Opus 5.5 | $0.00005 | $0.00090 |
| Sonnet 5.5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
constitution-reference 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 1mo 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.
What it actually says
Constitution Reference
Location
The project constitution lives at .specify/memory/constitution.md.
How to Read
Always use the Read tool to load the FULL constitution before any validation. Never validate from memory or assumptions.
What to Extract
When reading the constitution, identify:
- Stack Principles — What technologies are mandated and their usage patterns
- Engineering Principles — How code should be written (TDD, type safety, simplicity)
- AI Collaboration Principles — How human and AI work together (gates, approval flow)
- Quality Gates — What must pass before a phase is considered complete
If Constitution Doesn't Exist
If .specify/memory/constitution.md does not exist or is empty:
- Report that no constitution has been established
- Recommend editing
.specify/memory/constitution.mddirectly - Do NOT proceed with validation — there is nothing to validate against
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.
- 1mo ago First seen · 33 lines · 13 tokens per session scan A 9bd11c2ec6d4
constitution-reference is a skill published in the GitHub repository zachjxyz/jvn (2 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 224 once invoked, about $0.0001 per session on Opus 5.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
repo-visuals
Create hero visuals — animated GIF, static PNG, or animated SVG — for GitHub repositories. Runs a structured discovery conversation (scan repo → recommend format → propose creative scenarios → agree on a brief), then designs bespoke HTML/SVG, previews it in the browser, and exports. Use when the user asks for a README…
hyper-plan
Use when about to start a non-trivial implementation that needs decomposition before coding. Also when the user invokes /hyperclaude:hyper-plan. Produces an ordered, bite-sized plan in .hyperclaude/plans/ — the input for /hyperclaude:hyper-plan-review and /hyperclaude:hyper-implement.
hyper-interview
Use when starting from a vague or under-specified idea and want requirements clarified before planning — "interview me", "ask me what you need", "clarify requirements first", "I'm not sure exactly what I want", "make sure you understand before building". Also when the user invokes /hyperclaude:hyper-interview. Runs a…
cc-changelog
This skill should be used when the user asks to check for new Claude Code releases, "what changed in Claude Code", "any Claude Code updates", "check the changelog", "diff the Claude Code version", or wants the Claude Code changelog reviewed for changes relevant to THIS repo (the hyperclaude plugin). Reads a…
codex-changelog
This skill should be used when the user asks to check for new Codex CLI (codex-cli) releases, "what changed in Codex", "any Codex updates", "check codex releases", "diff the codex version", or wants Codex CLI releases reviewed for changes relevant to THIS repo's Codex bridge. Reads a locally-stored last-checked…
hyper-docs-sync
Use after implementation changes documented API, schemas, CLI flags, or architecture — before docs go stale. Also when the user invokes /hyperclaude:hyper-docs-sync. Syncs docs to the current code state.