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-costnpx skills add Dragoon0x/usemindit --skill mindit-costgit 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-cost)<a href="https://agentmods.dev/skills/dragoon0x/usemindit/mindit-cost"><img src="https://agentmods.dev/badge/skills/dragoon0x/usemindit/mindit-cost.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.00110 | $0.01203 |
| Opus 5 | $0.00055 | $0.00602 |
| Sonnet 5 | $0.00022 | $0.00241 |
| Haiku 4.5 | $0.00011 | $0.00120 |
Grade A, and why
mindit-cost 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindit-cost
The sixth of the eight forces. Run this when the question is "what does this actually cost."
The force
Designs have a sticker price (the engineering hours to build them) and a lifetime price (the support, maintenance, and debt they leave behind). The sticker price is almost always lower than the lifetime price. A custom one-off component is cheap to design and expensive to maintain for the next five years.
Cost asks: of the price this design will charge over its lifetime, how much has the team actually budgeted for?
A high cost is not automatically a bad thing. Some designs are worth it. Cost surfaces the bill so the team can decide whether it is.
When to run this
- The user is choosing between two designs and asks which is "cheaper" or "more practical."
- The user introduces a new component, third-party library, or custom pattern and wants a review.
- The user uses words like "complexity," "maintenance," "debt," "support burden," "is this worth it."
- The user is in a constrained team (small eng team, late-cycle, low budget) and wants to know what to cut.
How to analyze
-
Inventory what is new. What components, dependencies, integrations, animations, or interactions does this design introduce that did not exist before?
-
Estimate the four costs. For each criterion below, ask both the sticker cost and the lifetime cost. Sticker is "what does it cost to ship this once." Lifetime is "what does it cost to keep this working for two years."
-
Surface the support burden. Walk through the flows the design adds, and ask: where will a confused user end up? In a docs page that does not exist yet? In an inbox? On a Slack channel? The support cost is paid in tickets per week.
-
Surface the maintenance burden. Ask: who maintains this in a year? Is it a third-party dependency that needs version bumps? Is it a custom component nobody on the current team built?
-
Check
anti-patterns.yaml. -
Write the artifact.
Rubric
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.
- 5d ago First seen · 85 lines · 110 tokens per session scan A c88a6d637427
mindit-cost is a skill published in the GitHub repository Dragoon0x/usemindit (2 stars, last pushed 3mo ago), licensed MIT. It adds 110 tokens to every session and 1,203 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…