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/github-actionsnpx skills add DJRHails/dotfiles --skill github-actionsgit 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.00096 | $0.02702 |
| Opus 5 | $0.00048 | $0.01351 |
| Sonnet 5 | $0.00019 | $0.00540 |
| Haiku 4.5 | $0.00010 | $0.00270 |
Grade B, and why
github-actions scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
## The runner has no sudo — make tooling hermetic Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`pipx`, `cargo`, `bun` or `actionlint` on PATH. It *does* have git, curl, node, How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions conventions
Default: jobs run on taffy's self-hosted pool. GitHub-hosted runners are billed per minute and are the exception, taken deliberately and with a comment saying why.
This exists because the account drifted to $1.02/day on hosted Linux minutes
while nominally "using self-hosted runners" — 61% of it one repo whose ci.yml
had never been migrated. Silent drift back to paid runners is the failure mode
every rule below is shaped against.
The two runs-on forms
Copy one of these. Do not invent a third.
Private repo:
runs-on: >-
${{ vars.CI_FALLBACK == 'true'
&& 'ubuntu-latest'
|| fromJSON('["self-hosted", "linux", "x64", "taffy"]') }}
Public repo whose workflow has a pull_request trigger — a fork PR runs
arbitrary code and must never reach taffy:
runs-on: >-
${{ ((github.event_name == 'pull_request'
&& github.event.pull_request.head.repo.full_name != github.repository)
|| vars.CI_FALLBACK == 'true')
&& 'ubuntu-latest'
|| fromJSON('["self-hosted", "linux", "x64", "taffy"]') }}
A public workflow with no pull_request trigger (release, nightly sync) needs no
guard — only people with write access can fire it.
Two traps in that guard, both of which shipped broken once:
- Compare repo names; never use
github.event.pull_request.head.repo.fork. That flag asks "is the head repo a fork of anything", not "did this PR come from elsewhere".DJRHails/agent-browserandpi-interactive-subagentsare themselves forks of their upstreams, so the flag is permanently true there and routed every job to the billed runner — a silent, total no-op of the migration that only showed up by reading.labelson a finished job. github.event_name == 'pull_request' &&is load-bearing. On push,github.event.pull_requestis null, sohead.repo.full_nameis null, andnull != 'DJRHails/repo'is true — without the event check, every push would route to hosted.
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 · 219 lines · 96 tokens per session scan B c2b671af796f
github-actions is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed 7d ago), licensed MIT. It adds 96 tokens to every session and 2,702 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). 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…