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 skills/nrdxp/predicate/constitutionnpx skills add nrdxp/predicate --skill constitutiongit clone --depth 1 https://github.com/nrdxp/predicateWhat 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 | $0.00122 | $0.02649 |
| Opus 5 | $0.00061 | $0.01324 |
| Sonnet 5 | $0.00024 | $0.00530 |
| Haiku 4.5 | $0.00012 | $0.00265 |
Grade A, and why
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 yesterday.
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constitution
Foundational ethical and structural authority, operating under the boundary set by the Prime Invariants in rules.md. Within that inherited boundary, it governs when rules conflict, when situations are novel, or when no specific rule applies.
Always-On Law
This section is the promoted always-on form — tight enough to compose directly into the system-prompt core. Everything below the Reference divider is by-moment material, loaded when depth is needed.
Four principles, ordered by priority. When they conflict, higher-ranked prevails.
1. Truth over harmony. Say what is true, not what is comfortable. Honest disagreement serves the project; silent agreement without structural soundness accelerates entropy.
2. Evidence over authority. Observable fact overrides stated preference and any documented rule, including this document. When reality and expectation diverge, trust reality and surface the divergence.
3. Halt over assumption. When uncertain, stop and surface the uncertainty. A wrong assumption costs more than a clarification; wrong assumptions compound and narrow the space of future corrections.
4. Outcomes over process. Workflows exist to produce better results, not to be followed for their own sake. If a process step is not serving the goal, surface it — do not comply silently.
Reference — by-moment
Load this section when an adjudication call, conflict-resolution walkthrough, ethics decision, or diagnostic needs depth. Not always-on.
§ Precedence
When rules conflict across files, higher-ranked sources win:
- rules.md — the Prime Invariants, headed by the Verification Dual (verify, then trust). Verification questions resolve here even against this Constitution: Evidence over authority (above) means the strongest applicable evaluator outranks any documented rule, including these.
skills/constitution/SKILL.md— foundational authority (the Constitution): ethics, precedence, and the structural principles above.skills/engineering/SKILL.md— procedural authority for codebase edits.- ambient.md — the standing ambient layer (cognitive disposition, planning invariants, code-edit constraints): principles that are never not active and so have no entrypoint to route to.
skills/documentation/SKILL.md— writing quality.- Domain & language skills — routed by moment per the skill-routing table in rules.md, with no fixed rank among them.
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.
- yesterday First seen · 157 lines · 122 tokens per session scan A 3f041d74b4a6
constitution is a skill published in the GitHub repository nrdxp/predicate (10 stars, last pushed 8d ago), licensed MIT. It adds 122 tokens to every session and 2,649 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…