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.
git clone --depth 1 https://github.com/David405/harness-kitWrote 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/rules/david405/harness-kit/no-stage-harness-files)<a href="https://agentmods.dev/rules/david405/harness-kit/no-stage-harness-files"><img src="https://agentmods.dev/badge/rules/david405/harness-kit/no-stage-harness-files/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/rules/david405/harness-kit/no-stage-harness-files"><img src="https://agentmods.dev/badge/rules/david405/harness-kit/no-stage-harness-files.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.00418 | $0.00418 |
| Opus 5.5 | $0.00167 | $0.00167 |
| Sonnet 5.5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
no-stage-harness-files 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 2mo 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.
What it actually says
Staging policy
Never stage
Harness working state: the contracts directory, local session state, the feature ledger when it is used as working memory, and local notes. Keep them local unless the human explicitly asks to commit a specific one.
Stage after execute
When a contract reaches execute-complete with VERIFY green and harness review is done, stage the product files that contract touched: source, tests, specs, shipped documentation. Do not wait to be asked to stage.
Still do not commit unless the human explicitly asks (e.g. "commit", "commit and push").
Git publish gate (hard)
Never commit, push, or create/open a pull request without explicit human approval for that action.
- Contract approval, feature PASS, "approve", "proceed", or VERIFY green do not authorize commit, push, or PR — ask first or wait for an explicit publish instruction.
- After staging, stop and report what is ready. Offer commit/PR only as a question; do not run them.
git status/git difffor review prep are fine; publishing is not.
Commit authorship
When a commit is made, its author and committer are the human. Never a tool, assistant, editor or
bot identity, and no attribution trailer in the body — no "generated with", no "made with" or "made
by", no Co-Authored-By naming a tool.
The commit records what changed and why. What typed it is not part of the record.
After staging
Say briefly what was staged and what was left unstaged. Do not commit, push, or open a pull request unless the human explicitly requests that step.
When staging a feature branch, exclude harness paths even when they appear beside real changes.
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.
- 2mo ago First seen · 47 lines · 418 tokens per session scan A a1f716600bd8
no-stage-harness-files is a cursor rule published in the GitHub repository David405/harness-kit (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 418 tokens to every session, about $0.0017 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 cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.