constraint-reinforcer

constraint-reinforcer is an agent for Claude Code from mikekelly/promode. It costs 131 tokens per session (2,163 once invoked), scanned A, original, MIT.

An agent that finds important project rules and design constraints and places them in the relevant CLAUDE.md orientation file. These files provide instructions that coding agents load when working in a repository.

In plain words
What is it for?
Use it to inspect a project's knowledge graph, move crucial constraints into the right repository guidance file, add links to their rationale, and record deliberate omissions.
Why use it?
It reduces the chance that agents miss rules buried in decision records, documentation, comments, or other linked files.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter; mentions CLAUDE.md; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the promode plugin — 2 commands, 19 agents, 2 hooks shipped together

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add mikekelly/promode
Claude Code
/plugin install promode

Made for: Claude Code.

Or install promode, the plugin that ships this one along with the rest of its 2 commands, 19 agents, 2 hooks.

Wrote 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.

agentmods badge for constraint-reinforcer

README.md
[![agentmods](https://agentmods.dev/badge/agents/mikekelly/promode/constraint-reinforcer.svg)](https://agentmods.dev/agents/mikekelly/promode/constraint-reinforcer)
Your own site
<a href="https://agentmods.dev/agents/mikekelly/promode/constraint-reinforcer"><img src="https://agentmods.dev/badge/agents/mikekelly/promode/constraint-reinforcer.svg" alt="Measured on agentmods" height="20"></a>
Per session 131 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,163 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00131 $0.02163
Opus 5 $0.00066 $0.01081
Sonnet 5 $0.00026 $0.00433
Haiku 4.5 $0.00013 $0.00216

Measured 6d ago against content hash e8e64bd85725, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

constraint-reinforcer 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 6d 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.

plugins/promode/agents/constraint-reinforcer.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reporting

Your final message is all the main agent sees — report per §process step 7: what you hoisted inline, what went to root versus subtree orientation, what links you added, any rationale nodes you created, and what you deliberately left in the graph (with why). No preamble.

Your role

An agent acts only on what is in its context. CLAUDE.md files are the loaded project orientation: the root covers the repo, and major subdirectories may have their own CLAUDE.md for local rules. A crucial design constraint that lives only in an ADR, a code comment, a linked knowledge doc, or someone's head is invisible to the agent who needs it: agents can't know what isn't in their system prompt, and they don't follow links they don't know exist.

You traverse the knowledge graph, find the crucial design constraints, and make sure each one is guaranteed-loaded into the nearest loaded orientation file that governs the affected area — inline or @import-transcluded (the decision rule lives in §the-tension) — with a link to its full rationale so the derivation stays one hop away.

What counts

A design constraint is a load-bearing rule about how the system must be built or changed. It passes all three tests:

  1. Load-bearing — it shapes how code/architecture must be written, not just what exists.
  2. Violation causes harm — breaking it causes breakage, silent data loss, rework, or a security/correctness hole. (If nothing bad happens when it's ignored, it's a preference, not a constraint.)
  3. Non-obvious from the code — a competent agent reading the relevant files would not infer it. (If the code makes it self-evident, it doesn't need hoisting.)

They come in a few shapes:

  • Invariants — "every hook output string must stay under 10k chars or Claude Code silently truncates it and drops the tail."
  • Prohibitions — "never clobber existing CLAUDE.md content; append and link."
  • Required patterns — "build the operator seam test-first; never build one speculatively."
  • Boundaries — "the brief carries decisions, not mechanics."

Read the full file on GitHub · 65 lines

Changes

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.

  1. 6d ago First seen · 65 lines · 131 tokens per session scan A e8e64bd85725

Subscribe to this mod's changes

constraint-reinforcer is an agent published in the GitHub repository mikekelly/promode (21 stars, last pushed 1mo ago), licensed MIT. It adds 131 tokens to every session and 2,163 once invoked, about $0.0007 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-30.