agentleFS
sasuketoriisasuketorii/rev_harness_public/.cursor/rules/revharness-critical.mdc

rev_harness_public / rules

Cursor rule0 starsChanged 3 months agoApache-2.0View on GitHub

This rule is always applied to every Cursor agent session in this repository. It encodes fail-closed RevHarness invariants. Detailed operational guidance lives in revharness-detailed.mdc (description- based attach). Do not print tokens, keys, credentials, PII, or raw sensitive payloads. Examples include AKIA*, ghp_*, sk-*, and -----BEGIN PRIVATE KEY-----. When a detected value must be referenced, use redacted preview format: <prefix4>...<suffix4> (len=N). Treat any violation as a RevHarness security boundary failure. Cursor agents in this session must not invoke scripts/codex-wrapper.sh or scripts/claude-wrapper.sh.…

The file

We split this revharness-critical.mdc into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not print tokens, keys, credentials, PII, or raw sensitive payloads.

    line 14
  2. Very specific:

    When a detected value must be referenced, use redacted preview format: <prefix4>...<suffix4> (len=N).

    line 17
  3. Distinctive:

    Treat any violation as a RevHarness security boundary failure.

    line 19
  4. Distinctive:

    When shell execution would reference either wrapper path, refuse it.

    line 27
  5. Very specific:

    When invoked with --mode ask, do not write files or run shell commands.

    line 31
  6. Very specific:

    If an operation needs file changes, respond exactly: this requires --mode agent or --role agent — please re-invoke.

    line 32
  7. Distinctive:

    Do not declare completion from wrapper success or rule guidance alone.

    line 40
  8. Very specific:

    Do not modify, delete, rename, normalize, or regenerate .shared/project_id.

    line 46
  9. Distinctive:

    Keep this identity artifact stable for the full project lifecycle.

    line 48
  10. Distinctive:

    If it is missing or malformed, fail closed and report the blocker.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
revharness-critical.mdc
---
alwaysApply: true
---

# RevHarness Critical Invariants (Cursor)

This rule is **always applied** to every Cursor agent session in this
repository. It encodes fail-closed RevHarness invariants. Detailed
operational guidance lives in `revharness-detailed.mdc` (description-
based attach).

## No raw secrets in output

Do not print tokens, keys, credentials, PII, or raw sensitive payloads.
Examples include `AKIA*`, `ghp_*`, `sk-*`, and
`-----BEGIN PRIVATE KEY-----`.
When a detected value must be referenced, use redacted preview format:
`<prefix4>...<suffix4> (len=N)`.
Treat any violation as a RevHarness security boundary failure.

## No outbound cross-family wrapper invocation

Cursor agents in this session must not invoke `scripts/codex-wrapper.sh`
or `scripts/claude-wrapper.sh`.
Delegation to another agent family is owned by the orchestrator
(Claude or Codex top-level), not by Cursor.
When shell execution would reference either wrapper path, refuse it.

## `--mode ask` invocation = strict read-only

When invoked with `--mode ask`, do not write files or run shell commands.
If an operation needs file changes, respond exactly:
`this requires --mode agent or --role agent — please re-invoke`.
Tracked and untracked file modifications are forbidden in ask mode.

## Truth matrix is acceptance authority

`docs/manual/verification-truth-matrix.md` is the source of truth for
acceptance, LGTM, and completion.
Do not declare completion from wrapper success or rule guidance alone.
Completion requires execution evidence for the required deterministic
checks named by the applicable slice or matrix.

## `.shared/project_id` is immutable

Do not modify, delete, rename, normalize, or regenerate
`.shared/project_id`.
Keep this identity artifact stable for the full project lifecycle.
If it is missing or malformed, fail closed and report the blocker.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.