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/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/rules/andr-ca/agentharness/project-bootstrap)<a href="https://agentmods.dev/rules/andr-ca/agentharness/project-bootstrap"><img src="https://agentmods.dev/badge/rules/andr-ca/agentharness/project-bootstrap/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/andr-ca/agentharness/project-bootstrap"><img src="https://agentmods.dev/badge/rules/andr-ca/agentharness/project-bootstrap.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.00061 | $0.01110 |
| Opus 5.5 | $0.00024 | $0.00444 |
| Sonnet 5.5 | $0.00012 | $0.00222 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
project-bootstrap 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Bootstrap
Use this the first time the harness runs in a project, or whenever the owner asks you to set it up, tailor it, or figure out which conventions apply here.
The deterministic work is done by agentharness bootstrap. Your job is
the conversation — the tool inventories the repository and lists the
decisions that need making; you ask the owner about them, one at a time,
and feed the answers back.
Check the command exists first: agentharness bootstrap plan --help.
If it is unavailable, this repository has not installed the harness CLI —
fall back to tools/setup/harness-link.sh and assess the project
conversationally rather than claiming a bootstrap flow exists.
The loop
# 1. Inventory (read-only — writes nothing, safe to run any time)
agentharness bootstrap plan --json
# 2. Feed answers back as you collect them
agentharness bootstrap plan --answer rigor.tier=production
# 3. Apply, only with the hash of the plan the owner approved
agentharness bootstrap apply --answer ... --confirm <plan_hash>
plan is safe to re-run at any point. Re-run it after every answer — the
question set and the proposed actions both change as answers come in.
Reading the plan
{
"detected": [{"capability": "test", "present": true,
"detail": "pytest", "evidence": ["pyproject.toml"]}],
"questions": [{"id": "rigor.tier", "prompt": "...", "default": "production"}],
"actions": [{"path": "ruff.toml", "summary": "Create ruff.toml"}],
"is_resolved": false,
"plan_hash": "..."
}
| Field | What it means |
|---|---|
detected |
Verified facts. present: true means a config file says so, and evidence names it. |
questions |
Decisions only the owner can make. Unanswered ones block apply. |
actions |
Exactly what apply would create. Empty until answers ask for something. |
is_resolved |
False while any question is unanswered. |
plan_hash |
Changes whenever the repo or the answers change. |
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 · 113 lines · 61 tokens per session scan A 7e219c93cbc3
project-bootstrap is a cursor rule published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 1,110 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-09-03.
Other cursor rules, from other repositories
03-journal-format
Journal format and coordination rules.
workflow-examples
CRITICAL: Contains mandatory examples for correct workflow implementation. DO NOT assume workflow patterns without consulting this documentation first.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.