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-continuitynpx skills add Dragoon0x/usemindit --skill mindit-continuitygit 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-continuity)<a href="https://agentmods.dev/skills/dragoon0x/usemindit/mindit-continuity"><img src="https://agentmods.dev/badge/skills/dragoon0x/usemindit/mindit-continuity.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.00122 | $0.01137 |
| Opus 5 | $0.00061 | $0.00568 |
| Sonnet 5 | $0.00024 | $0.00227 |
| Haiku 4.5 | $0.00012 | $0.00114 |
Grade A, and why
mindit-continuity 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 3d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindit-continuity
The second of the eight forces. Run this when the question is "does this fit the system that exists."
The force
Continuity asks whether the new thing extends the system the user already knows, or accidentally forks it. Every product has invisible contracts: a button looks like that button, a date picker behaves like that date picker, an error message uses those words. When a new screen breaks one of those contracts without an explicit reason, users feel the seam even if they can't name it. Multiply that by a few features and the product feels like four products glued together.
Continuity is not about preventing novelty. It is about making novelty intentional. Break a convention only when you can name what you are breaking and why the break is worth the friction.
When to run this
- The user is adding a feature, page, or component to an existing product.
- The user pastes two screenshots and asks "do these feel like the same product."
- The user uses words like "consistent," "fits," "feels off," "different vibe," "matches the rest."
- The user is deciding whether to reuse an existing component or build a new one.
- The user is reviewing a design system PR.
How to analyze
-
Anchor in the system. Identify the existing product the new design lives in. If the user has not shared examples of existing screens or pointed at the design system, ask once for at least one reference surface before scoring.
-
Walk the five alignments. For each of the criteria below, compare the new design against the system. Note specific divergences with file or screen names where possible.
-
Distinguish intentional from accidental breaks. A break with a stated reason is a different finding than a break that happened because nobody noticed. Surface both. Score on whether the break was deliberated, not whether it exists.
-
Open
anti-patterns.yaml. Match findings to registered patterns. -
Compute and write the artifact. See "Output format."
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.
- 3d ago First seen · 74 lines · 122 tokens per session scan A 3f12cc8df76e
mindit-continuity is a skill published in the GitHub repository Dragoon0x/usemindit (2 stars, last pushed 3mo ago), licensed MIT. It adds 122 tokens to every session and 1,137 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…