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/e2e-doc-syncnpx skills add iamcxa/kc-claude-plugins --skill e2e-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/e2e-doc-sync)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/e2e-doc-sync"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/e2e-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.00054 | $0.02764 |
| Opus 5 | $0.00027 | $0.01382 |
| Sonnet 5 | $0.00011 | $0.00553 |
| Haiku 4.5 | $0.00005 | $0.00276 |
Grade A, and why
e2e-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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Doc Sync — Documentation Gap Scanner, Writer & Verifier
Routing
| Input | Route |
|---|---|
| bare invocation | → Full Sync |
--fix |
→ Full Sync (alias for bare — kept for backward compat) |
--check |
→ Report Only (no writes) |
--probe-only |
→ Verify Existing Docs (skip Phases 1-3 and 5, run Phase 4 on all existing docs, then Phase 6) |
--auto |
→ Full Sync (skip confirmation) |
--section <doc-file> |
→ Targeted Sync (one doc file) |
--diff <ref> |
→ Use explicit git diff base instead of auto-detect |
Phase 1: Static Scan
Step 0 — Diff-Aware Pre-Processing (automatic)
Before inventorying files, compute a diff of changed skill/agent content since the last version tag. This catches behavioral branches and other features that surface-level extraction (flags, headings) would miss.
Find diff base:
# Auto-detect: find the most recent e2e-pipeline version tag
DIFF_BASE=$(git -C ${CLAUDE_PLUGIN_ROOT} tag -l "e2e-pipeline-v*" --sort=-v:refname | head -1)
# If --diff <ref> provided, use that instead
# If no tags exist, use HEAD~10 as fallback — warn user: "No version tags found, using HEAD~10. Diff coverage may be incomplete for older changes."
Extract changed content:
git -C ${CLAUDE_PLUGIN_ROOT} diff ${DIFF_BASE}..HEAD \
-- 'skills/*/SKILL.md' 'agents/*.md' \
| grep '^+' | grep -v '^+++' | sed 's/^+//'
Group added lines by source file. Cap diff summary at 2000 chars.
Step 1 — Inventory & Cross-Reference
- Read
references/doc-sync-context.md→ load Source Map, Doc Structure, Probe Config, 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
agents/*.md→ for each: extract agent name, tools, input contract fields, dispatch trigger - 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
- If diff summary exists: additionally check whether diff-added content has doc coverage
- Orphan check: source files found in Step 2 inventory but absent from Source Map → classify as Critical gap ("source exists, no Source Map entry — doc target unknown"). Include file path and inferred doc target in gap report. This catches newly added skills/agents that Phase 5 hasn't registered yet.
- 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
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 · 190 lines · 54 tokens per session scan A ab3995730c0f
e2e-doc-sync is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 2,764 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
__SKILL_ID__
This fixture verifies that skill content can be written into the target sandbox and queried back immediately.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…