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 eaglesakura/agent-skills --skill read-documentgit 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/read-document)<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/read-document"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/read-document/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/read-document"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/read-document.svg" alt="Reviewed on agentmods" width="80" 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.00147 | $0.01023 |
| Opus 5 | $0.00073 | $0.00511 |
| Sonnet 5 | $0.00029 | $0.00205 |
| Haiku 4.5 | $0.00015 | $0.00102 |
Grade A, and why
[object Object] 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 7d 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
{領域} / {ドキュメント群の入口}
この SKILL は、列挙したドキュメントを いつ正本から読むか を決める索引である。
判断材料は必ず正本(対象ドキュメント)から取る。本 SKILL 本文に内容要約を置かない。
読み方・深さ・出力の取り方は markdown-search に従う(本 SKILL で再掲しない)。
「いつ読むか」は frontmatter の description に集約する。本文でトリガーを重複定義しない。
使わないか
- {隣接するが別 SKILL / 別文書群の方が適切な場面}
- (「いつ使うか」は
descriptionを正とする)
対象ドキュメント
- {表示名}
docs/architecture/another.mdrepo:example/docs/architecture/overview.md
読み方
- 適用時は対象 path を解決したうえで、必ず
markdown-searchを使う(Stage・スクリプト・出力の正本) - プロンプト制約がある場合は、索引全体ではなく制約に合う文書・節から進める
- path 解決:
workspace-resolve-file-path/workspace-resolve-root-directory
境界
- 対象: 上表ドキュメントを正本として読むこと
- 対象外: {この SKILL が引き受けない隣接領域。委譲先 SKILL があれば名を書く}
- 対象外: 対象ドキュメントの内容を本 SKILL 本文へ要約・再掲すること
- 対象外:
markdown-searchの手順・出力形式の再定義 - 文書の新規作成・lint 修正は
markdown-documentation/markdown-fixに委譲する
関連
- 段階ロード・把握手順・出力の正本:
markdown-search - パス解決:
workspace-resolve-file-path/workspace-resolve-root-directory - {隣接 SKILL があれば列挙}
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.
- 7d ago First seen · 69 lines · 147 tokens per session scan A 56788b6eaf9c
[object Object] is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 147 tokens to every session and 1,023 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-09-04.
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…
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…
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…