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 rules/andr-ca/agentharness/committinggit clone --depth 1 https://github.com/andr-ca/agentharnessWhat 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.00037 | $0.01345 |
| Opus 5 | $0.00018 | $0.00673 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00135 |
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 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 — 108 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.
- yesterday First seen · 108 lines · 37 tokens per session scan A c05db0e057bb
committing is a cursor rule published in the GitHub repository andr-ca/agentharness (1 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,345 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 cursor rules, from other repositories
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
handoff
Export a Waybill Bundle by default, or import one when explicitly requested.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
lemoncrow.execute
LemonCrow execute mode reference for Cursor.
prompt-routing
Route tasks to the correct Universal AI Engineering Prompt.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.