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 Eliyce/paqad-ai --skill documentation-sync-enginegit clone --depth 1 https://github.com/Eliyce/paqad-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/eliyce/paqad-ai/documentation-sync-engine)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/documentation-sync-engine"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/documentation-sync-engine.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.00029 | $0.00853 |
| Opus 5 | $0.00015 | $0.00426 |
| Sonnet 5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
documentation-sync-engine 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 6d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Acts as the canonical entry point for post-implementation documentation sync. Runs diff-doc-sync first to narrow to actually-stale canonical doc paths, then dispatches each path to the domain-specific maintainer (api, integration, error catalog, canonical, or glossary). Aggregates the results into a single report so the caller does not have to invoke five skills sequentially.
The point is to give callers one place to ask "sync the docs after this change" and get consistent, deduplicated output every time.
Use This When
Use this after implementation lands (or just before handoff) on feature-development, bug-fix, refactor, or migration workflows. Skip when differential_refresh is disabled in the project profile and the team prefers running the per-domain skills directly.
Inputs
- Read the changed file list at
changed_files. - Use the detector at
detector_script_path(viadiff-doc-sync) to produce the stale canonical doc set. - Read
references/orchestration-rules.mdbefore dispatching so the routing rules and execution order stay consistent across runs. - When
target_domainsis non-empty, intersect the dispatched set with the requested domains.
Procedure
- Invoke
diff-doc-syncwith the changed file list to produce the candidate stale doc set (JSON array). - Pipe that array's paths into
scripts/route-paths.shto assign each path a delegate domain (api | integration | error | glossary | canonical); seeassets/routing-table.txtfor the mapping. - Apply
target_domainsfiltering if provided. - Invoke each delegate skill once with only its domain's paths.
- Aggregate delegate outputs and format per
assets/output.template.md. - Validate with
scripts/lint-output.sh.
Output Contract
- Return a heading named
Documentation Sync. - Provide a
Stale Doc Setline:Detected: {N} | Routed: {M} | Skipped (target_domains filter): {K}. - For each domain that ran, emit a third-level heading
### {domain}and list the paths the delegate updated, plus any consistency warnings the delegate raised. - Provide a
Known Driftaggregated section pulling from delegates' deferred-drift notes. - When the stale set is empty, return
Documentation Sync: no canonical docs require update.exactly.
What ships with it
6 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.
- 6d ago First seen · 80 lines · 29 tokens per session scan A cc9f7a2b84aa
documentation-sync-engine is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 853 once invoked, about $0.0001 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
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.
agent-pipeline
Multi-agent pipeline orchestration skill.