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/nominal-io/instro/mintlify-apinpx skills add nominal-io/instro --skill mintlify-apigit clone --depth 1 https://github.com/nominal-io/instroWhat 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.00026 | $0.00264 |
| Opus 5 | $0.00013 | $0.00132 |
| Sonnet 5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
mintlify-api 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.
What it actually says
Mintlify API
Use the Mintlify API to manage documentation sites programmatically. This skill covers deployment management, build triggers, and site metadata queries.
Authentication
All API requests require an API key passed in the Authorization header:
Authorization: Bearer <your-api-key>
Generate API keys from the Mintlify dashboard under Settings > API Keys.
Core capabilities
Trigger deployments
Programmatically trigger a documentation rebuild when your codebase changes outside of Git push events.
Query site metadata
Retrieve information about your documentation site including deployment status, configured domains, and navigation structure.
Manage preview deployments
Create and manage preview deployments for pull requests and branches to review documentation changes before they go live.
Resources
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 · 44 lines · 26 tokens per session scan A 084b97ab0d32
mintlify-api is a skill published in the GitHub repository nominal-io/instro (664 stars, last pushed 3d ago), licensed Apache-2.0. It adds 26 tokens to every session and 264 once invoked, about $0.0001 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.
Other skills, from other repositories
mcp-sigrok
Skill "mcp-sigrok" from daedalus/mcp-sigrok, covering mcp-sigrok skill, usage, examples, list available drivers and scan for devices.
instrument-tektronix-scope
Standard protocol for Tektronix Mixed Domain (MDO) and Mixed Signal (MSO) oscilloscopes.
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.