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/eliyce/paqad-ai/diff-doc-syncnpx skills add Eliyce/paqad-ai --skill diff-doc-syncgit 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/diff-doc-sync)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/diff-doc-sync"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/diff-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.00016 | $0.00515 |
| Opus 5 | $0.00008 | $0.00258 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
diff-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.
What it actually says
What It Does
Narrows documentation follow-up to only the canonical docs made stale by the current diff, avoiding full documentation refreshes when differential_refresh is enabled.
Use This When
Use this after implementation or validation when you already know which files changed and only want the stale canonical documentation set.
Inputs
- Read the changed file list from
changed_files. - Read
references/diff-sync-rules.mdfor project-specific override rules before deciding whether a doc can be safely skipped.
Procedure
- Pipe the changed file list into
scripts/detect-stale-docs.sh— it cross-references against existing canonical docs and emits candidate paths. - Drop any paths that
references/diff-sync-rules.mddeclares safe to skip in this scenario. - Format as a JSON array exactly matching
assets/output.template.json(sorted, duplicate-free). - Validate with
scripts/lint-output.sh— it enforces JSON shape, sortedness, dedupe, and.mdsuffix.
Output Contract
- Match
assets/output.template.json: a JSON array of canonical doc paths.[]exactly when none are stale. - Output must pass
scripts/lint-output.sh(exit 0).
Escalate / Stop Conditions
- Ask when the changed file list is missing or incomplete.
- Warn when the stale doc detector is unavailable or returns non-canonical paths.
- Do not widen the result to a full documentation workflow unless the detector evidence requires it.
Resources
references/diff-sync-rules.mdscripts/detect-stale-docs.shscripts/lint-output.shassets/output.template.jsonagents/openai.yaml
What ships with it
5 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.
- 5d ago First seen · 66 lines · 16 tokens per session scan A db4c26a21ece
diff-doc-sync is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 515 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
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.