agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.cursor/rules/hermes-mobile-prevention-july-2026.mdc

mac-yolo-safeguards / rules

Cursor rule3 starsChanged 4 days agoMITView on GitHub

July 2026 session recurrence prevention for Hermes Mobile agents

  • Reads credentials

The file

We split this hermes-mobile-prevention-july-2026.mdc into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not spawn subagents for the same file domain, PR merge, or research already done in the parent turn.

    line 13
  2. Very specific:

    Check plan.md §2 before Task — if (in_progress) by another agent, STOP or hand off via vault Handoffs/.

    line 14
  3. Very specific:

    Read hermes-mobile/docs/proofs/continuous/latest.json before "fixed" / "works on device".

    line 22
  4. Very specific:

    If e2e=skipped in latest.json, report it — do not claim device UX verified.

    line 29

≈ “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
hermes-mobile-prevention-july-2026.mdc
---
description: July 2026 session recurrence prevention for Hermes Mobile agents
globs: hermes-mobile/**/*
alwaysApply: false
---

# Hermes Mobile — prevent recurrence (July 2026)

Full playbook: [hermes-mobile/docs/PREVENT-RECURRENCE-JULY-2026.md](../../hermes-mobile/docs/PREVENT-RECURRENCE-JULY-2026.md).

## Cursor single-pass (no duplicate subagents)

- Do **not** spawn subagents for the same file domain, PR merge, or research already done in the parent turn.
- Check `plan.md` §2 before `Task` — if `(in_progress)` by another agent, **STOP** or hand off via vault `Handoffs/`.
- One parent per lock domain; parallelize **disjoint** files only.

## Session gates (agent runs — never user homework)

1. Vault pull + newest `Handoffs/` before multi-file Hermes work.
2. `bash hermes-mobile/scripts/agent-adb-refresh.sh` before phone/pair claims.
3. `bash hermes-mobile/scripts/agent-pre-asc-edit.sh` before any ASC review notes edit.
4. Read `hermes-mobile/docs/proofs/continuous/latest.json` before "fixed" / "works on device".
5. `node tools/agent-session-start.js --full` before ship language.

## Hard bans

- ASC notes: no gateway URLs, tailnet hostnames, or API keys — `hermes://setup?demo=1` only.
- Multi-Mac: `node tools/hermes-mobile-pair.js --mini-tailscale` — never laptop `.env` key on mini URL.
- If `e2e=skipped` in `latest.json`, report it — do not claim device UX verified.

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.