agentleFS
putervisionputervision/agent-reasoning-mcp/.cursor/rules/behavior-mcp.mdc

agent-reasoning-mcp / rules

Cursor rule22 starsChanged 47 days agoMITView on GitHub

This project uses behavior-mcp with project slug "agent-reasoning-mcp" to execute deterministic behavior trees at ~60Hz in browser runtimes with reactive triggers and safety guardrails.

The file

We split this behavior-mcp.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Load Behavior: Call load_behavior(action: "load", behavior_name: "...") to activate execution.

    line 7
  2. Very specific:

    Monitor Execution: Check get_status(action: "current") and inspect active node traversal paths.

    line 8
  3. Very specific:

    Safety & Abort: Call abort_behavior(action: "abort") to immediately halt execution if anomalous behavior occurs.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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
behavior-mcp.mdc
<!-- behavior-mcp:start -->
# Behavior Runtime Engine (behavior-mcp)

This project uses `behavior-mcp` with project slug "agent-reasoning-mcp" to execute deterministic behavior trees at ~60Hz in browser runtimes with reactive triggers and safety guardrails.

## Mandatory Runtime Workflow
1. **Load Behavior**: Call `load_behavior(action: "load", behavior_name: "...")` to activate execution.
2. **Monitor Execution**: Check `get_status(action: "current")` and inspect active node traversal paths.
3. **Reactive Triggers**: Register high-priority emergency interrupts via `register_trigger(action: "register", ...)`.
4. **Safety & Abort**: Call `abort_behavior(action: "abort")` to immediately halt execution if anomalous behavior occurs.

## 10 Core MCP Tools
- `load_behavior`: Inject and start behavior tree execution.
- `set_parameters`: Update execution parameters on the fly.
- `get_status`: Query active status, current node path, and tick counters.
- `abort_behavior`: Immediately halt, pause, or resume execution.
- `register_trigger`: Configure priority interrupts with cooldown guards.
- `replay_recording`: Capture and replay deterministic frame actions.
- `get_metrics`: Query execution telemetry and duration statistics.
- `manage_behaviors`: Register and version behavior tree definitions with SHA-256 tree hashes.
- `manage_blackboard`: Read and write behavior tree blackboard state variables.
- `manage_runtime_db`: Database maintenance, diagnostics, and SHA-256 Merkle audit verification.
<!-- behavior-mcp:end -->

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.