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/djrhails/dotfiles/slidesyncnpx skills add DJRHails/dotfiles --skill slidesyncgit clone --depth 1 https://github.com/DJRHails/dotfilesWhat 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.00154 | $0.03069 |
| Opus 5 | $0.00077 | $0.01535 |
| Sonnet 5 | $0.00031 | $0.00614 |
| Haiku 4.5 | $0.00015 | $0.00307 |
Grade A, and why
slidesync 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 yesterday.
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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
slidesync
Sync a Slidev markdown deck to/from Google Slides, building native Slides
objects (title/body/bullets/tables/positioned images, brand-styled text boxes) —
so the result stays editable, not a flat image. pull reconstructs the markdown
from those native objects; roundtrip proves the loop is stable.
Packaged at github.com/DJRHails/slidesync
(PyPI: slidesync). Run with
uvx slidesync — no install needed.
Auth (no setup)
Borrowed from gog: OAuth client id/secret resolved cross-platform from
~/.config/gogcli/credentials.json (Linux/XDG), falling back to
~/Library/Application Support/gogcli/credentials.json (macOS) — and the
keyring-password file at either location — mirroring gog's own resolution.
Refresh token via gog auth tokens export. The stored token already carries
slides+drive scopes. Requires the Slides API enabled on the gog Cloud
project.
The account defaults to gog's default account (override with --account or
$SLIDESYNC_ACCOUNT).
Commands
| Command | Purpose |
|---|---|
slidesync push <file.slidev.md>... [--deck ID] [--new "Title"] [--anchor SLIDE] [--prune] [--force] |
md -> Slides (rejected if it would discard live Slides edits; --force overrides) |
slidesync pull <deckId> --out <file.md> [--all] |
Slides -> md (--all includes non-managed slides) |
slidesync sync <file.slidev.md>... [--deck ID] [--prune] |
reconcile with the live deck: capture comment threads as <!-- @Author: ... -->, write live edits back into the markdown, push local changes; conflicts print three-way diffs and exit 1 |
slidesync comments <deckId> |
list comment threads as JSON (page anchor, author, content, replies) |
slidesync roundtrip [--keep] |
self-test: push a sample, pull, assert identical |
slidesync layouts <deckId> |
list a deck's theme layouts + placeholders |
slidesync make-templates <deckId> |
inject legacy in-deck {{token}} template slides |
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.
- yesterday First seen · 195 lines · 154 tokens per session scan A a8e18b77541d
slidesync is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed 7d ago), licensed MIT. It adds 154 tokens to every session and 3,069 once invoked, about $0.0008 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
autopilot-batch
Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds, Fable reviews Fable builds).
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
qa-handoff
Generate a hands-on QA testing guide as a self-contained HTML page — for Rails apps or static (Hugo) sites. --publish uploads the HTML to the project's configured QA host.
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
dustoff
Assess a project that's been dormant for months and produce a prioritized re-entry plan — lifecycle stage, what's stale or broken, and how far the project's tooling has drifted from current conventions — delegating every fix to the skill that owns it, and optionally capturing the plan as a tracking issue that survives…