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/eaglesakura/agent-skills/markdown-documentationnpx skills add eaglesakura/agent-skills --skill markdown-documentationgit clone --depth 1 https://github.com/eaglesakura/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/eaglesakura/agent-skills/markdown-documentation)<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/markdown-documentation"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/markdown-documentation.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.00136 | $0.00973 |
| Opus 5 | $0.00068 | $0.00487 |
| Sonnet 5 | $0.00027 | $0.00195 |
| Haiku 4.5 | $0.00014 | $0.00097 |
Grade A, and why
markdown-documentation 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
ドキュメンテーション / 技術文書の記載
技術ドキュメントの読み手は後続の実装・レビュー Agent である。
文体・必須セクション・実在コード引用を揃えることで、検索（markdown-search）とレビューが安定する。
いつ使うか / 使わないか
- 使う:
docs/等の技術文書、アーキテクチャ・規約・ナレッジの作成更新 - 使わない:
.ai-agent/plan/の要件・詳細設計（engineer.*）、単なる lint 修正（markdown-fix）、探索のみ（markdown-search）
ひな形は assets/template.md を起点にする。
基本方針
- 「である」調で簡潔に書く
- 本文は
DO/推奨を示し、DO NOTはナレッジベース（や example）に寄せる - 実装例は実在コードを優先し、架空コードで埋めない
必須構造
- 概要（冒頭）— 目的・役割・特徴・関連コンポーネント
- 原則・規則（必要な数だけ）— 各原則に次を付ける
${原則名}の補足（意図・利点・注意・例外）${原則名}の実装例（良い例必須、悪い例は必要時）
- ナレッジベース（末尾付近、参考リンクの直前）—
### DO:/### DO NOT: - 参考リンク（Web を参照した場合）— URL は
<https://...>形式
見出しは文書内で一意にする（「補足」「実装例」の重複を避ける）。階層は最大 4、飛ばさない。
作業手順
- 既存コードと類似ドキュメントを調査する（必要なら先に
markdown-search） - テンプレートに沿いドラフトを書く
- コード引用・パスは references/code-blocks.md に従う
- 作図・パス表記は references/diagrams-and-paths.md に従う
- 必須セクションと見出し一意性を確認する
- references/lint-and-validation.md を確認し、仕上げに
markdown-fixを実行する
アプリ基盤の書き方
- 量産不要な基盤は「実装済み・詳細は参照先」と短く書く
- 実装者が使う情報に焦点を当て、基盤内部の長文実装例は避ける
詳細リファレンス
| ファイル | 内容 |
|---|---|
| references/code-blocks.md | コード引用・テンプレート・ディレクトリツリー |
| references/lint-and-validation.md | リンターと整合性チェック |
| references/diagrams-and-paths.md | Mermaid・相対パス |
What ships with it
5 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.
- 3d ago First seen · 63 lines · 136 tokens per session scan A 7e646bd7d72b
markdown-documentation is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 136 tokens to every session and 973 once invoked, about $0.0007 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…