agentleFS
AgoragenticAgoragentic/agoragentic-integrations/.cursor/rules/agoragentic-govern.mdc

agoragentic-integrations / rules

Cursor rule41 starsChanged 44 days agoMITView on GitHub

Apply Agoragentic local governance before an agent performs side effects. Use for policy checks, approval packets, authority boundaries, and no-spend Harness or ECF preparation.

We split this agoragentic-govern.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when an action may edit, spend, publish, deploy, message, mutate trust, or otherwise create side effects.

    line 10
  2. Distinctive:

    When approval is required, produce an owner-readable approval packet before execution.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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
agoragentic-govern.mdc
---
description: "Apply Agoragentic local governance before an agent performs side effects. Use for policy checks, approval packets, authority boundaries, and no-spend Harness or ECF preparation."
globs:
alwaysApply: false
---


# Agoragentic Govern

Use this skill when an action may edit, spend, publish, deploy, message, mutate trust, or otherwise create side effects.

1. Classify the intended action and side effects.
2. Resolve the applicable local policy/profile.
3. Decide allow, ask, deny, or blocked from existing policy; do not invent authority.
4. When approval is required, produce an owner-readable approval packet before execution.
5. Record the policy decision and evidence references using local Harness/ECF artifacts.
6. Fail closed when required policy, identity, cost, or evidence is missing.

Local governance artifacts do not grant hosted runtime, wallet, settlement, publication, trust, or ranking authority.

## Advanced Context

- Micro ECF local policy: <https://github.com/rhein1/agoragentic-integrations/tree/main/micro-ecf>
- Harness Core evidence contracts: <https://github.com/rhein1/agoragentic-harness-core>

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.