A set of operating rules for coding agents working with the AXIOM-MESH project. It defines how setup, configuration, and privileged actions are handled.

Use it to guide agents during project setup, configuration, and changes that could affect repositories, deployments, or production systems.

It helps prevent an agent from treating available tools, credentials, or connections as permission to make changes. It also keeps runtime and dependency choices within the project's supported boundaries.

How Zoverions/AXIOM-MESH configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to Zoverions/AXIOM-MESH. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Zoverions/AXIOM-MESH/main/.cursorrules

Clone the repo

git clone --depth 1 https://github.com/Zoverions/AXIOM-MESH

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/zoverions/axiom-mesh/cursorrules/github.svg)](https://agentmods.dev/rules/zoverions/axiom-mesh/cursorrules)

Your own site

<a href="https://agentmods.dev/rules/zoverions/axiom-mesh/cursorrules"><img src="https://agentmods.dev/badge/rules/zoverions/axiom-mesh/cursorrules/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/zoverions/axiom-mesh/cursorrules"><img src="https://agentmods.dev/badge/rules/zoverions/axiom-mesh/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 808 This file is loaded in full into every session.

When invoked 808 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00808	$0.00808
Opus 5.5	$0.00323	$0.00323
Sonnet 5.5	$0.00162	$0.00162
Haiku 4.5	$0.00081	$0.00081

Measured 1mo ago against content hash f1b308f0e817, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cursorrules 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.

.cursorrules · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AXIOM-MESH Agent Instructions

Capability is not authority. Discovery is not permission. Connection is not permission.

This file is the concise machine-facing operating guide for coding agents and automated contributors working with AXIOM-MESH. It does not grant repository, runtime, deployment, merge, or production authority.

Installation

Use the supported root setup command:

npm run setup

The supported Node.js line is pinned by .node-version and the package engine declarations. Do not substitute an unreviewed runtime or dependency tree merely because it works locally.

Configuration

Start from .env.example when local configuration is required. Treat credentials, tokens, provider configuration, production resolver mappings, and external destinations as authority-bearing material rather than ordinary convenience settings.

The supported privileged-effect path is:

Gateway -> Hypervisor -> Sandbox -> Grid

Do not create a parallel authority path around that sequence. Agent runtimes, adapters, discovery protocols, credentials, and reachable tools are clients or capabilities; they are not independent sources of permission.

Usage

Before changing supported behavior:

Read README.md and AGENT-ENTRY.md.
Read CONTRIBUTING.md for repository authority and contribution rules.
Inspect mesh/config/capabilities.json before changing a capability claim.
Inspect docs/security/CURRENT-BUILD-THREAT-MODEL.md for the current trust boundary.
Run narrow relevant checks while iterating.
Run the full supported validation before presenting the change as ready:

npm run check npm run release:verify

For a read-only pre-action authority assessment, see agent-skills/axiom-authority-auditor/SKILL.md.

Authority rules for automated contributors

A request to draft or propose a change is not permission to merge it.
Repository write access is not production authority.
A passing test is evidence about the tested claim; it is not production promotion.
Do not activate providers, egress, remote execution, public endpoints, credentials, production resolver mappings, or deployment surfaces unless the governing change explicitly authorizes that activation.
Do not weaken a failing safety or documentation boundary merely to make a proposed change pass.
Missing, ambiguous, stale, or conflicting authority for a consequential external effect must not be converted into permission.
Sensitive security findings belong in the process described by SECURITY.md, not in a public proof-of-concept.

Read the full file on GitHub · 76 lines

Changes

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 · 76 lines · 808 tokens per session scan A f1b308f0e817

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository Zoverions/AXIOM-MESH (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 808 tokens to every session, about $0.0032 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-08-31.

ai-agents audit-log authenticated-capabilities capability-security cryptographic-evidence fail-closed

AXIOM-MESH: Cursor rule for Cursor

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

AXIOM-MESH Agent Instructions

Installation

Configuration

Usage

Authority rules for automated contributors

What this file has done since we first saw it

Other cursor rules, from other repositories

theauth

infra-deploy

testing

sdk-integrations-mcp

coding-standards

ai-knowledge-base