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/iamcxa/kc-claude-plugins/kc-plugin-forge-doc-syncnpx skills add iamcxa/kc-claude-plugins --skill kc-plugin-forge-doc-syncgit clone --depth 1 https://github.com/iamcxa/kc-claude-pluginsWrote 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/iamcxa/kc-claude-plugins/kc-plugin-forge-doc-sync)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-plugin-forge-doc-sync"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-plugin-forge-doc-sync.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.00059 | $0.01331 |
| Opus 5 | $0.00030 | $0.00665 |
| Sonnet 5 | $0.00012 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
kc-plugin-forge-doc-sync 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kc-plugin-forge-doc-sync
Routing
| Input | Route |
|---|---|
| bare invocation | → Full Sync |
--check |
→ Report Only |
--auto |
→ Full Sync (skip confirmation) |
--section <doc-file> |
→ Targeted Sync (one doc file) |
Phase 1: Static Scan
- Read
reference/doc-sync-context.md→ load Source Map, Doc Structure, Post-Sync Hooks - Inventory source files:
- Glob
skills/*/SKILL.md→ for each: extract skill name, description, all--flags, modes (from routing tables), key concepts - Glob
hooks/→ for each: extract event type, trigger condition, affected tools
- Glob
- Inventory documentation:
- Glob
docs/*.md+README.md→ for each: extract title, section headings, mentioned features, example count
- Glob
- Cross-reference: for each Source Map entry, search its Doc Target for coverage of every extracted feature
- Classify gaps:
- Critical: source feature exists, zero mention in any doc
- Warning: mentioned in one doc but not explained (e.g., flag listed in table but no usage guide)
- Info: documented but could be improved (missing example, stale cross-reference)
- Meta-doc consistency check: verify CLAUDE.md skill/agent counts, README docs table completeness, plugin.json description accuracy
If --section <doc-file>: filter Source Map to entries targeting that doc file only.
Output: gap_report + feature_inventory
Phase 2: History Enrichment
Prerequisite: MCP tools episodic-memory and private-journal. If unavailable, skip Phase 2 with warning: "History enrichment skipped — MCP tools unavailable. Running static-only mode." Proceed to Phase 3 with unenriched gaps.
- Search episodic memory:
search("kc-plugin-forge")→ extract usage patterns, user workflows, reported issues - Search journal:
search_journal("kc-plugin-forge")→ extract technical insights, debug findings, failed attempts - Read MEMORY.md → extract known plugin knowledge entries
- Enrich each gap:
- History mentions this feature with usage context? → add context to gap (improves doc writing quality)
- History contradicts current docs? → escalate gap to
accuracy_risk(priority fix)
- Features found in history but NOT in gap report → add as new Info-level gap ("undocumented but used")
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.
- 5d ago First seen · 126 lines · 59 tokens per session scan A 5850472152dd
kc-plugin-forge-doc-sync is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,331 once invoked, about $0.0003 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.
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…