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/patch-stack-actionnpx skills add DJRHails/dotfiles --skill patch-stack-actiongit 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.00046 | $0.02599 |
| Opus 5 | $0.00023 | $0.01300 |
| Sonnet 5 | $0.00009 | $0.00520 |
| Haiku 4.5 | $0.00005 | $0.00260 |
Grade A, and why
patch-stack-action 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patch Stack
Manage patch-stack forks powered by DJRHails/patch-stack-action.
When to use
- The repo references
DJRHails/patch-stack-actionin a workflow - Commits on
mainare prefixed withpatch-stack: - The repo has
patch/*branches - The user wants to set up a new patch-stack fork
Concepts
A patch-stack fork maintains a clean separation between upstream code and your changes:
| Branch | What it is |
|---|---|
base (or configured name) |
Read-only mirror of upstream main. Updated automatically by the nightly sync. Never commit to this directly. |
patch/* |
One branch per logical change. Each is rebased onto base automatically. This is where you do your work. |
main |
The integration branch. Built automatically: base + all patches squash-merged (prefixed patch-stack:). Never commit to this directly except fork: prefixed commits for fork-specific infra. |
Key rule: main is rebuilt from scratch on every sync. Only fork: prefixed commits and patch-stack: squash-merges survive. All real work happens on patch/* branches.
Day-to-day patch editing workflow
Creating a new patch
Every patch needs three things: a patch/* branch from base, a push, and a local PR targeting base.
# 1. Always branch from base, not main
git checkout -b patch/my-feature origin/base
# 2. Make your changes, commit
git add <files>
git commit -m "feat(scope): description"
# 3. Push
git push origin patch/my-feature
# 4. ALWAYS create a PR targeting base (not main)
gh pr create --head patch/my-feature --base base
The PR against base is required. The sync action uses it to track patch state, generate squash commit messages on main, and link to upstream PRs. Without it the patch is invisible to the workflow.
Editing an existing patch
# Check out the patch branch
git checkout patch/my-feature
# Or use a worktree to avoid leaving main
git worktree add .data/worktrees/my-feature patch/my-feature
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 · 303 lines · 46 tokens per session scan A 720500ea26c6
patch-stack-action is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 2,599 once invoked, about $0.0002 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…