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 andr-ca/agentharness --skill committinggit clone --depth 1 https://github.com/andr-ca/agentharnessWrote 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/andr-ca/agentharness/committing)<a href="https://agentmods.dev/skills/andr-ca/agentharness/committing"><img src="https://agentmods.dev/badge/skills/andr-ca/agentharness/committing/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/andr-ca/agentharness/committing"><img src="https://agentmods.dev/badge/skills/andr-ca/agentharness/committing.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.00040 | $0.01359 |
| Opus 5.5 | $0.00016 | $0.00544 |
| Sonnet 5.5 | $0.00008 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
committing 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Committing
Full reference: .github/COMMITTING_GUIDELINES.md (examples, git aliases,
commit template). This skill is the actionable summary.
Before you commit
git statusandgit diff— know exactly what you're about to commit.- Stage specific files, not
git add ./git add -Ablind. git diff --cached— review staged content one more time, scan for secrets (API keys, tokens, passwords).- Let hooks run. Never
--no-verify, never--no-gpg-sign. If a hook fails, fix the underlying issue and re-stage — don't bypass it.
Writing the commit
- Atomic: one logical change per commit. Don't mix a feature, a fix, and a refactor in one commit.
- Message explains WHY, not WHAT — the diff already shows what changed.
- Imperative mood summary ("Add X", not "Added X"), ideally under ~50 chars, blank line, then body wrapped at ~72 chars if more explanation is needed.
- Reference issues (
Fixes #123,Relates to #456) when applicable.
What never gets committed
- Secrets: API keys, tokens, passwords, private credentials.
.envand its variants — but DO commit.env.sample(sanitized template).- Debug code: stray
console.log/print, commented-out code, debugger statements. - Build artifacts,
node_modules/, and anything covered by.github/.gitignore.template.
After the commit — run the completion gate, then follow publish authority
-
Run
bash tools/check-completion.sh— all quality gates must pass before declaring work done. This is enforced by the Stop hook in.github/hooks/completion-gate.json(Copilot) and.claude/settings.json(Claude Code).This path is specific to the agentharness repo itself. If this skill file is symlinked/copied into a consumer project instead (the normal case — see
harness-link.sh),tools/check-completion.shdoes not exist there and will exit 127. Check for a generated, consumer-local completion gate first:[ -x .agentharness-bin/check ].harness-link.sh init/updategenerates this wrapper automatically forlink/submodule/npmmodes — runbash .agentharness-bin/checkin its place. It delegates to the resolved harness checkout's ownenforce-profilecommand against this project, not the harness's.--mode copyhas no live harness checkout to delegate to, so no wrapper exists there —harness-link.sh audit --json'scan_mechanically_enforcefield tells you up front whether a given install has one at all, rather than finding out mid-task. Either way, also run this project's own lint/type/test commands if it has any not covered by the gate. Don't silently skip verification just because the harness's own path doesn't resolve — find the equivalent for this repo.
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 · 112 lines · 40 tokens per session scan A a8c183aa986e
committing is a skill published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 1,359 once invoked, about $0.0002 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
stepwise-task-execution
Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a needrevision bounce.
incremental-commits
Commit boundaries and messages on a task branch. Use when deciding where to cut a commit or how to word one while implementing.
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
eb-activity-summary
Summarize activity for the Ephemeral Buffer MCP repository, including commits, pull requests, issues, releases, and CI. Use for EB weekly or custom-period activity reports; do not use for implementing repository changes.
layerfs-js-sdk
Use when building, editing, testing or inspecting a project through LayerFS with the JavaScript SDK (@layerfs/agent) from the command line. Activates on LayerFS projects, Branches, Commits, Workspaces or Sandboxes; LayerFS.open, LayerFS.init, layerfs.project., layerfs.fs., layerfs.branch., layerfs.sandbox. or…