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 minorun365/my-claude-code-settings --skill sync-docsgit clone --depth 1 https://github.com/minorun365/my-claude-code-settingsWrote 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/minorun365/my-claude-code-settings/sync-docs)<a href="https://agentmods.dev/skills/minorun365/my-claude-code-settings/sync-docs"><img src="https://agentmods.dev/badge/skills/minorun365/my-claude-code-settings/sync-docs/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/minorun365/my-claude-code-settings/sync-docs"><img src="https://agentmods.dev/badge/skills/minorun365/my-claude-code-settings/sync-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00048 | $0.00647 |
| Opus 5.5 | $0.00019 | $0.00259 |
| Sonnet 5.5 | $0.00010 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
sync-docs 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 27d 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
ドキュメント同期（実装との整合性チェック）
プロジェクトのドキュメント（計画書・仕様書など）を実装コードと比較し、差異を修正してください。
対象ドキュメント
$ARGUMENTS が指定されていれば、そのパスのドキュメントを対象にしてください。 指定がなければ、以下の順でドキュメントフォルダを探してください：
docs/documents/- プロジェクトルートの
*.mdファイル
チェック項目
- 進捗状況: ステップやフェーズの完了状態は実装と一致しているか
- 機能一覧: チェックボックスの状態は正確か
- ディレクトリ構成: 記載されているファイル・フォルダは実際に存在するか
- 技術スタック: 使用ライブラリ・バージョンは正しいか
- 設定値: テーマ、リージョン、モデルIDなどの設定は実装と一致しているか
- ツール・API定義: 実装されている機能とドキュメントの記載が一致しているか
- システムプロンプト: 記載内容と実装が一致しているか
作業手順
- まず Explore エージェントを使って、ドキュメントと実装の差異を網羅的に調査
- 発見された差異を一覧にまとめる
- 差異がある箇所を Edit ツールで修正
- 最後に変更内容のサマリーを報告
注意事項
- 実装が正で、ドキュメントを実装に合わせる方向で修正する
- 未実装の機能は「Phase 2」や「今後の拡張」に移動する
- 軽微な差異（未使用コードの残存など）も報告するが、優先度を明示する
次のステップ
ドキュメントを更新したら、グローバルナレッジベースへの反映も提案してください：
「ドキュメントを同期しました。プロジェクト固有でない汎用的な学びがあれば、グローバルナレッジベースにも反映しておく？」
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.
- 27d ago Changed · -1 lines 9ea8a244ed5d
- 1mo ago First seen · 49 lines · 48 tokens per session scan A 79700865aa77
sync-docs is a skill published in the GitHub repository minorun365/my-claude-code-settings (142 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 647 once invoked, about $0.0002 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…