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/aj604/toolshed/scheduling-doc-syncnpx skills add aj604/toolshed --skill scheduling-doc-syncgit clone --depth 1 https://github.com/aj604/toolshedWhat 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 | $0.00096 | $0.13578 |
| Opus 5 | $0.00048 | $0.06789 |
| Sonnet 5 | $0.00019 | $0.02716 |
| Haiku 4.5 | $0.00010 | $0.01358 |
Grade A, and why
scheduling-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 3d 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 — 742 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduling Doc Sync
Overview
Installs the shipped automation into a target repo — five workflows:
doc-audit.yml— the scheduled, read-only audit. Derives its scope from the registry, runs the audit engine, publishes a validated report as an artifact and a job summary. Writes nothing.doc-bloat-audit.yml— the weekly, read-only bloat audit. Preflights the registry, plans through the engine's public contract, fans its chunks out to budgeted workers, and publishes the report's typed completion truth. Writes nothing.doc-apply.yml— the manual apply dispatch. A reviewer names the record digests they approve from one audit run; the lane mints the approval set from that selection, plans, applies, and opens a pull request.doc-policy-apply.yml— the audit-chained policy lane. It wakes only after a successful scheduled drift audit and only acts when the consumer committed.doc-lifecycle/auto-apply-policy.json; the engine derives the eligible subset, and the lane opens a real pull request whose review is the semantic review. An absent policy is a clean opt-out, not a permissive default.doc-sync-upgrade.yml— the self-upgrade lane, three jobs split by who decides and who holds credentials. Its weekly schedule only compares the installed version to the plugin's latest release and files one notice issue naming a newer one; regenerating the wiring runs solely on aworkflow_dispatchcarrying that version astarget, and lands as a review PR.
You install wiring; you do not re-derive it. Orchestration lives in the shipped workflow
YAML; every lifecycle rule — scope, verdict contract, approval, application — lives in the
doclifecycle engine package (plugins/doc-lifecycle/engine/README.md), vendored into the
install and reached only through its public CLI. Every run-surface string lives in a shipped
script: render-audit-summary.py for the audit lanes, render-apply-summary.py for the apply
lane, render-report.py for the upgrade lane; the upgrade lane's version comparison and the
shape-check on its dispatched target live in upgrade-gate.py, and which paths an upgrade may
write in stage-upgrade.py. Never inline audit or apply method into workflow YAML — that forks
the method from its one owner.
What ships with it
15 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.
- doc-apply.yml 37 KB
- doc-audit.yml 28 KB
- doc-bloat-audit.yml 18 KB
- doc-policy-apply.yml 28 KB
- doc-sync-upgrade.yml 21 KB
- scripts/apply-upgrade.py 31 KB runs code
- scripts/bloat-cadence.py 12 KB runs code
- scripts/check-repo-integrity.py 7.4 KB runs code
- scripts/probe-evidence-tool.py 9.5 KB runs code
- scripts/render-apply-summary.py 52 KB runs code
- scripts/render-audit-summary.py 13 KB runs code
- scripts/render-report.py 14 KB runs code
- scripts/stage-upgrade.py 21 KB runs code
- scripts/upgrade-gate.py 4.7 KB runs code
- scripts/verify-apply-bytes.py 36 KB runs code
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.
- 3d ago First seen · 742 lines · 96 tokens per session scan A 2e67b36a8326
scheduling-doc-sync is a skill published in the GitHub repository aj604/toolshed (2 stars, last pushed 27d ago), licensed MIT. It adds 96 tokens to every session and 13,578 once invoked, about $0.0005 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
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
linea-dependency-maintenance
Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions, release-age policies, audits, CI validation, Dependabot boundaries, PRs, and GitHub tracking issues. Use whenever the user…
cicd-supply-chain
Use when attacking or auditing a CI/CD pipeline or software supply chain — pwn requests, poisoned pipeline execution, compromised/mutable-tag actions, dependency confusion, registry worms, runner backdoors, OIDC trust abuse, SLSA/provenance.
oss-debug-ci
Debug CI failures in unfamiliar repo pipelines. Reads CI configs, fetches failure logs, classifies the failure type, and guides the user through diagnosing and fixing the issue. Use when CI fails on your PR in an OSS repo, when you don't understand a CI error, or when debugging GitHub Actions/CircleCI/other CI…
megalinter-setup
Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks". Always goes through npx mega-linter-runner (--install or --upgrade), then…
pr-watch-fix
Watch the GitHub PR for the current branch, wait for CI to finish, and autonomously fix failing jobs by reading logs, editing sources, and pushing. Stops cleanly when stuck.