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 skills add eigent-ai/agent-skills --skill mintlify-docs-updatergit clone --depth 1 https://github.com/eigent-ai/agent-skillsWrote 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/eigent-ai/agent-skills/mintlify-docs-updater)<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/mintlify-docs-updater"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/mintlify-docs-updater.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.1 | $0.00071 | $0.00671 |
| Opus 5 | $0.00036 | $0.00336 |
| Sonnet 5 | $0.00014 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
mintlify-docs-updater 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 8d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mintlify Docs Updater
Overview
Use this skill to ingest user-provided Markdown into the Mintlify docs tree, enforce required frontmatter, and update navigation entries in docs/docs.json.
Prefer the included script for deterministic page placement and nav updates.
Workflow
- Read the current site map in
references/docs-structure.md. - Decide the destination page path (for example,
core/new-feature->docs/core/new-feature.md). - Ingest the uploaded Markdown file with the script:
python3 scripts/ingest_markdown_doc.py \
--source /absolute/path/to/upload.md \
--page core/new-feature \
--group "Core"
- Use
--subgroup "Models"when adding pages undercore/models. - Use
--dry-runfirst when the target placement is uncertain. - Validate changes:
- Confirm the new file exists under
docs/. - Confirm
docs/docs.jsonincludes the new"/path/to/page"entry in the right group. - Confirm frontmatter includes
titleanddescription.
- Confirm the new file exists under
Commands
Add a new page and nav entry:
python3 scripts/ingest_markdown_doc.py \
--source /absolute/path/to/upload.md \
--page get_started/advanced-setup \
--group "Get Started"
Add a new Core > Models page and place it after an existing page:
python3 scripts/ingest_markdown_doc.py \
--source /absolute/path/to/model-guide.md \
--page core/models/new-provider \
--group "Core" \
--subgroup "Models" \
--insert-after /core/models/kimi
Preview changes without writing files:
python3 scripts/ingest_markdown_doc.py \
--source /absolute/path/to/upload.md \
--page troubleshooting/new-issue \
--group "Troubleshooting" \
--dry-run
Editing Rules
- Keep page files in
docs/<section>/<slug>.md. - Keep page references in
docs/docs.jsonas absolute doc routes (for example,"/core/concepts"). - Keep frontmatter keys minimal and compatible with current docs:
title(required)description(required)icon(optional)
- Preserve existing Mintlify components and JSX blocks when present.
- Use
/docs/images/<file>for image paths in Markdown/HTML blocks.
What ships with it
3 files 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.
- 8d ago First seen · 81 lines · 71 tokens per session scan A 32a694440ffe
mintlify-docs-updater is a skill published in the GitHub repository eigent-ai/agent-skills (19 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 671 once invoked, about $0.0004 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
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…