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/cboone/agent-harness-plugins/prnpx skills add cboone/agent-harness-plugins --skill prgit clone --depth 1 https://github.com/cboone/agent-harness-pluginsWhat 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.00098 | $0.04135 |
| Opus 5 | $0.00049 | $0.02067 |
| Sonnet 5 | $0.00020 | $0.00827 |
| Haiku 4.5 | $0.00010 | $0.00413 |
Grade A, and why
pr 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 2d 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR
Commit, push, and create a pull request in one automated step. Never prompt the user for input — make opinionated decisions at every step.
Workflow
1. Gather Context
First, detect the repository's base branch:
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
If gh is not available or the command fails, fall back to:
git remote show origin | grep 'HEAD branch' | sed 's/.*: //'
Use the detected value as <default-branch>.
Detect the PR base branch
The current branch may have been created from a non-default branch (e.g., for stacked PRs). Check the reflog for the branch creation point:
git reflog show $(git branch --show-current) --format='%gs' | tail -1
This produces output like branch: Created from develop, branch: Created from origin/develop, or branch: Created from refs/heads/feature/parent. If the last entry matches branch: Created from <name>, extract <name> and normalize it by stripping any refs/heads/, refs/remotes/origin/, or leading origin/ prefix.
If a source branch name was extracted, verify it is a valid base for the PR. Run these checks in order, stopping at the first failure:
-
Not the current branch: The source branch must differ from the current branch.
-
Exists on the remote: Note that
git ls-remotealways exits 0 regardless of whether the branch exists, so check for non-empty output:git ls-remote --heads origin <source-branch> | grep -q . -
Not already merged into the default branch: The source branch may have been merged into the default branch since this branch was created (e.g., a parent feature branch that has since landed). Check whether the source branch is an ancestor of the default branch:
git fetch origin <default-branch> <source-branch> --quiet git merge-base --is-ancestor origin/<source-branch> origin/<default-branch>If the exit code is 0, the source branch has been fully merged into the default branch. Skip it and use
<default-branch>as<base-branch>instead.
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.
- 2d ago First seen · 355 lines · 98 tokens per session scan A d1a9649016e2
pr is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 4,135 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
commit
Use when making any git commit. Always pass why the changes were made as the argument; when no reason was stated, pass the request that prompted the changes instead — never an invented why.
avatar-contribution-pr
Turn an avatar GitHub issue (from the in-app avatar-editor easter egg) into a merged sprite — validate the art, then either add a new module or replace an existing one, and open a PR that closes the issue. Handles both "Avatar contribution: " (a brand-new sprite) and "Avatar edit: " (a hand-redraw of an existing…
reconcile
Enforces Law 1 (Research Before Executing) of the 7 Laws of AI Agent Discipline. Establishes git ground truth — branch, status, stashes, worktrees, ahead/behind — before any mutation, halts on protected or destructive operations, then carries the known-good state through to a landed PR: stage by filename, commit one…
create-pr
コミット、push、Pull Request の作成を一つの手順で行う。「プルリクエストを作成」「PRを作成」などの要求で使用する。.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
commit
Create a Conventional Commit safely. Guards against committing to main, validates format, stages and commits. Chains to push-and-pr when user mentions push. Triggers: "commit", "/commit", "закоммить", "сделай коммит", "коммит и пуш", "commit and push".