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 j5ik2o/okite-ai --skill deepresearch-readmegit clone --depth 1 https://github.com/j5ik2o/okite-aiWrote 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/j5ik2o/okite-ai/deepresearch-readme)<a href="https://agentmods.dev/skills/j5ik2o/okite-ai/deepresearch-readme"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/deepresearch-readme/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/j5ik2o/okite-ai/deepresearch-readme"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/deepresearch-readme.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.00140 | $0.00838 |
| Opus 5 | $0.00070 | $0.00419 |
| Sonnet 5 | $0.00028 | $0.00168 |
| Haiku 4.5 | $0.00014 | $0.00084 |
Grade A, and why
deepresearch-readme 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 9d 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
Deepresearch Readme
GitHub OSS向けREADMEを、短時間で「何ができるか」と「どう始めるか」が伝わる状態に整える。
進め方
- 前提を確定する。
- プロジェクト種別を特定する: ライブラリ / CLI / Webアプリ / GitHub Action
- 対象読者を特定する: 利用者 / 評価者 / コントリビューター
- READMEの目的を確定する: 新規作成 / 改善 / レビュー
- ファーストビューを構成する。
- H1にプロジェクト名を書く
- 1〜2文で価値を書く（技術スタック説明より先に価値を出す）
- Quickstartへの最短導線を置く
- 必要な主要リンクだけを置く（Docs、Issues、Releases）
- Quickstartを最短化する。
Requirements、Install、Runの順で3〜6行程度に収める- 実際に実行できるコマンドだけを残す
- OS差分が長くなる場合は
docs/installation.mdへ分離する
- 構成を仕上げる。
- セクションは以下を基本とする:
HighlightsQuickstartUsageDocumentationGetting helpContributingLicense- 詳細説明は
docs/に切り出し、READMEには相対リンクだけ残す
- 最終検証を行う。
- 5分以内に「導入→最小実行」までたどれるか確認する
- リンク切れ、前提バージョン、手順の古さを確認する
references/readme-review-checklist.mdで網羅確認する
出力テンプレート
README本文を作るときは references/readme-template.md のテンプレートを優先して使う。
レビュー方針
既存READMEをレビューするときは以下を優先する。
- Critical
- Quickstartが実行不能
- 必須情報（What/How to start/Help）が欠落
- READMEが巨大化し、開始手順が埋もれている
- Warning
- セクション順が読み手の意思決定順とずれている
- docsへの導線が弱い
- バッジやリンクが多すぎて価値が伝わりにくい
- Info
- 表現の簡潔化
- 例の追加（CLI実行例、最小コード例）
- FAQやトラブルシューティングへの導線追加
参照ファイル
- 実践チェックリスト:
references/readme-review-checklist.md - README雛形:
references/readme-template.md
What ships with it
2 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.
- 9d ago First seen · 76 lines · 140 tokens per session scan A 621f70485f5f
deepresearch-readme is a skill published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 140 tokens to every session and 838 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-01.
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…