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-tracenpx skills add Dragoon0x/usemindit --skill mindit-tracegit 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-trace)<a href="https://agentmods.dev/skills/dragoon0x/usemindit/mindit-trace"><img src="https://agentmods.dev/badge/skills/dragoon0x/usemindit/mindit-trace.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.00125 | $0.01524 |
| Opus 5 | $0.00063 | $0.00762 |
| Sonnet 5 | $0.00025 | $0.00305 |
| Haiku 4.5 | $0.00013 | $0.00152 |
Grade A, and why
mindit-trace 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindit-trace
The third of three meta skills. Run this when the question is "how did we get here, and what depends on this."
What this skill does
Reads the decision artifacts already stored in .mindit/decisions/ and walks the graph defined by depends_on references. Surfaces the chain of reasoning behind a current design state. Lets the team answer "why did we decide X" by looking at the actual artifacts produced when X was decided, including the evidence cited at the time.
This is what mindit's stateful, file-based architecture exists for. Layers-style pure-prose skills cannot do this; mindit can.
When to run this
- The user asks "why did we decide X," "what was the reasoning behind Y."
- The user is about to change a decision and wants to know what else depends on it.
- The user is onboarding a new team member and wants to walk them through how the design got to its current state.
- The user is doing a retrospective and wants to revisit the evidence that backed prior decisions.
- The user asks for a "decision history," "decision chain," or "decision lineage."
How to analyze
-
Locate the starting decision. The user names a decision by ID (e.g.
clarity-20260311-checkout-cta) or by description ("the decision about the checkout CTA size"). If by description, search filenames and titles in.mindit/decisions/to find the match. If multiple match, ask which one. -
Walk backward (dependencies). Read the
depends_onfield of the starting artifact. For each dependency, load that artifact, read itsdepends_on, recurse. Stop when you reach artifacts with no further dependencies (root decisions) or when you have walked five levels deep, whichever comes first. -
Walk forward (consequents). Grep the
.mindit/decisions/directory for artifacts whosedepends_onincludes the starting decision's ID. Recurse the same way. -
Build the trace. Produce both:
- A backward chain: this decision was made because of X, which was made because of Y, which was made because of Z.
- A forward chain: this decision is referenced by A, which is referenced by B.
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 · 121 lines · 125 tokens per session scan A e427e739a353
mindit-trace is a skill published in the GitHub repository Dragoon0x/usemindit (2 stars, last pushed 3mo ago), licensed MIT. It adds 125 tokens to every session and 1,524 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…