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 skills add DJRHails/dotfiles --skill commitgit clone --depth 1 https://github.com/DJRHails/dotfilesWrote 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/djrhails/dotfiles/commit)<a href="https://agentmods.dev/skills/djrhails/dotfiles/commit"><img src="https://agentmods.dev/badge/skills/djrhails/dotfiles/commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/djrhails/dotfiles/commit"><img src="https://agentmods.dev/badge/skills/djrhails/dotfiles/commit.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00854 |
| Opus 5.5 | $0.00004 | $0.00342 |
| Sonnet 5.5 | $0.00002 | $0.00171 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
commit 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a git commit for the current changes using a concise Conventional Commits-style subject.
Format
<type>(<scope>): <summary>
typeREQUIRED. Usefeatfor new features,fixfor bug fixes. Other common types:docs,refactor,chore,test,perf.scopeOPTIONAL. Short noun in parentheses for the affected area (e.g.,api,parser,ui).summaryREQUIRED. Short, imperative, <= 72 chars, no trailing period.
Notes
- Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
- Do NOT include breaking-change markers or footers.
- Do NOT add sign-offs (no
Signed-off-by). - After committing, push to the current branch. Never push to
main/the default branch — if you are on it (and the repo's AGENTS.md/CLAUDE.md doesn't forbid branching), create a feature branch (<github-username>/<feature-name>) first, then push with-u. - Skip files containing secrets (
.env, credentials, tokens) and warn if any are staged. Skip.agents/settings.local.json/.claude/settings.local.json— add them to.gitignoreif not already ignored. - If it is unclear whether a file should be included, ask the user which files to commit.
- Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.
If CI doesn't start after a push
A push to a PR branch that spawns no workflow run is almost never a credential problem. Check the cheap causes first, in order:
- Conflicted PR —
gh pr view <n> --json mergeable,mergeStateStatus. A PR withmergeable: CONFLICTING/mergeStateStatus: DIRTYcreates nopull_requestruns at all: GitHub can't build therefs/pull/<n>/mergetest-merge commit those runs execute against. Merge or rebase the base branch, resolve, push — CI resumes on its own. - Trigger filters — read the workflow's
on:block.push: branches: [main]means feature-branch pushes get CI only via thepull_requestevent;paths:filters can skip a commit entirely. - Token type — only then suspect the credential (
gh auth status): an Actions-issuedghs_token suppresses workflow triggering; a user PAT (ghp_/github_pat_) does not.
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.
- 1mo ago First seen · 54 lines · 11 tokens per session scan A bd89e0c67ae7
commit is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 854 once invoked, about $0.0000 per session on Opus 5.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
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).
autopilot-triage
Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.
create-pr
Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.
global-commit
Create a git commit following Conventional Commits specification.
git-commit
This skill should be used BEFORE running any git commit command. Triggers when about to run git commit. Ensures commit messages follow Conventional Commits specification and prompts for the Jira ticket number.