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/dragoon0x/usemindit/mindit-constraintnpx skills add Dragoon0x/usemindit --skill mindit-constraintgit clone --depth 1 https://github.com/Dragoon0x/useminditWrote 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/dragoon0x/usemindit/mindit-constraint)<a href="https://agentmods.dev/skills/dragoon0x/usemindit/mindit-constraint"><img src="https://agentmods.dev/badge/skills/dragoon0x/usemindit/mindit-constraint.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 | $0.00117 | $0.01242 |
| Opus 5 | $0.00059 | $0.00621 |
| Sonnet 5 | $0.00023 | $0.00248 |
| Haiku 4.5 | $0.00012 | $0.00124 |
Grade A, and why
mindit-constraint 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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindit-constraint
The third of the eight forces. Run this when the question is "what hard limits is this honoring."
The force
Every design lives inside a fence. The fence is made of accessibility law, browser support targets, engineering capacity, platform guidelines, brand rules, performance budgets, and policy constraints. Designers cannot push the fence by ignoring it. The fence pushes back later, often through the legal team, the support inbox, or a launch slip.
Constraint asks: of the fences this design has to live inside, which ones did it design for and which ones did it design around?
When to run this
- The user asks "can we actually ship this," "is this realistic," or "what are we forgetting."
- The user mentions accessibility, WCAG, screen readers, contrast ratios, keyboard navigation, or focus rings.
- The user mentions performance, payload, latency, or "is this too heavy."
- The user mentions a platform: iOS, Android, watchOS, web embed, email client.
- The user mentions a legal or policy question: GDPR, CCPA, COPPA, accessibility law, content moderation, age gating.
- The user is reviewing brand-adjacent work and asks whether it stays inside brand rules.
How to analyze
-
Enumerate the fences. For the subject under review, list every hard limit that applies: WCAG target, browser support matrix, performance budget, engineering capacity, platform guidelines, brand rules, legal regimes, policy constraints. If the user has not stated these, ask once for the relevant ones before scoring.
-
Per-fence assessment. For each fence, score whether the design honors it, ignores it, or is silent on it. Silence is its own finding: a design that does not say what its keyboard behavior is has not made a decision about keyboard behavior.
-
Score the criteria below. Note that not every criterion applies to every subject. If a criterion is N/A (e.g. there is no native platform involved), give it the average score of the remaining criteria and note N/A in the criterion's note field.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 77 lines · 117 tokens per session scan A 323189d13f8a
mindit-constraint is a skill published in the GitHub repository Dragoon0x/usemindit (2 stars, last pushed 3mo ago), licensed MIT. It adds 117 tokens to every session and 1,242 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
accessibility-compliance-accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.
om-ds-guardian
Design System Guardian for Open Mercato. Use for frontend UI work, design-system compliance reviews, semantic token migration, hardcoded color or typography cleanup, DS-compliant page scaffolding, and common DS violations such as arbitrary text sizes, raw color classes, or missing shared states. Prefer this skill…
a11y-audit
Audit a component for WCAG AA accessibility compliance.
ss-review
Review UI code for design system compliance, accessibility, and best practices.
a11y-audit
Use to audit a component, file, or directory for WCAG 2.1 AA accessibility compliance. Detects ARIA anti-patterns, missing semantics, keyboard gaps, and color-only information. Safety-first — refuses to emit fixes that would create a new accessibility bug. Scope is always explicit; do not use for page-level flow or…
a11y-flow-audit
Use to audit a page, view, or composed flow for WCAG 2.1 AA compliance at the composition level - landmarks, heading hierarchy, tab order across components, focus handoff on modal open/close, live-region conflicts. Scope is page/view, NOT component internals. Safety-first - refuses to emit fixes that would create a…