constraint-check

A process auditor for coding-agent workflows. It checks whether required steps and restrictions were followed by examining the order of tool calls and other evidence.

In plain words
What is it for?
Reviewing invoked skills, checking tests and approvals, classifying violations as blocking or non-blocking, and suggesting fixes.
Why use it?
It catches missed approvals, incorrect step order, and other rule violations that an agent's own explanation might overlook.

Agent

Install

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.

agentmods
npx agentmods add agents/rune-kit/rune/constraint-check
Clone the repo
git clone --depth 1 https://github.com/Rune-kit/rune
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 230 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 $0.00031 $0.00230
Opus 5 $0.00015 $0.00115
Sonnet 5 $0.00006 $0.00046
Haiku 4.5 $0.00003 $0.00023

Measured 2d ago against content hash 4d38f73db833, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

constraint-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 2d 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.

agents/constraint-check.md · 26 lines

What it actually says

You are the constraint-check skill — Rune's process compliance auditor.

Quick Reference

Workflow:

  1. Identify all skills invoked during the workflow
  2. Load HARD-GATEs and numbered constraints from each skill's SKILL.md
  3. Audit compliance: tool call ordering (tests before code?), user approval, output capture
  4. Classify violations: HARD-GATE violation = BLOCK, Constraint = WARN, Best Practice = INFO
  5. Report compliance table per skill + remediation steps

Critical Rules:

  • MUST check ALL invoked skills (not just orchestrators)
  • Use tool call ordering (not agent narrative) to verify temporal constraints
  • MUST distinguish HARD-GATE violations (BLOCK) from constraint violations (WARN)
  • MUST NOT accept agent self-report — check independently via evidence

Read skills/constraint-check/SKILL.md for the full specification.

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. 2d ago First seen · 26 lines · 31 tokens per session scan A 4d38f73db833

Subscribe to this mod's changes

constraint-check is an agent published in the GitHub repository Rune-kit/rune (84 stars, last pushed 17d ago), licensed MIT. It adds 31 tokens to every session and 230 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

polymath

Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.

pjt222/agent-almanac · 25 tokens

insistir-reviewer

Cross-review agent for insistir multi-agent orchestration. Reviews another agent's implementation and sends structured findings to the lead. Read-only — cannot edit or write files. Can run verification commands (tests, typecheck, lint) via whitelisted Bash. Enforces quality without gatekeeping. Do NOT use directly …

JairoTorregrosa/jaiskills · 76 tokens

insistir-researcher

Research agent for insistir orchestration. Researches best practices, framework documentation, and codebase patterns. Read-only — cannot edit or write files. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 50 tokens

insistir-learnings-researcher

Knowledge search agent for insistir multi-agent orchestration. Searches docs/solutions/ for past solutions relevant to a query using grep-first strategy with parallel keyword searches including synonyms. Read-only — cannot edit, write, or execute commands. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 68 tokens

insistir-worker

Implementation agent for insistir multi-agent orchestration. Implements a task or applies review fixes, commits, reports to lead. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 42 tokens

askit-explorer

Surveys a repository broadly and reports a structural map of its components and layout. Use when delegating broad read-only exploration - the bounded discovery role for answering what exists and how a repo is organized.

product-on-purpose/agent-skills-toolkit · 45 tokens