Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/pinoox/neuromesh/agent-rulegit clone --depth 1 https://github.com/pinoox/neuromeshWrote 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.
[](https://agentmods.dev/rules/pinoox/neuromesh/agent-rule)<a href="https://agentmods.dev/rules/pinoox/neuromesh/agent-rule"><img src="https://agentmods.dev/badge/rules/pinoox/neuromesh/agent-rule.svg" alt="Measured on agentmods" height="20"></a>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.00699 | $0.00699 |
| Opus 5 | $0.00349 | $0.00349 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade C, and why
agent-rule scanned grade C with 1 finding 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 yesterday.
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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Same body as docs/agent-guide.md “Universal instructions”. Install help: docs/agent-guide.md --> How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NeuroMesh context
This workspace has the NeuroMesh MCP server. Prefer it for reading and exploring code so the agent gets folded skeletons and targeted symbols instead of multi-thousand-line files.
Default loop (v0.9.0 — zero-embed fast engine)
Default: retrieval.engine: fast — graph index + query-side lexical expansion. No ONNX at index or MCP startup. Pass the task as written only — no keywords / expansion.
get_context_packetwithquery/task_description/prompt/taskas written. Optional:path_hints/entity_types.- Check
retrieval.resolution_tier— expectlexical_primaryor graph-assisted seeds on NL prompts (notembedding_primaryunless repo owner setengine: hybrid). - If
coverage.claimispartial,no_seed_resolved, orno_confident_match, followpacket_gaps/next—neuromesh_expand_gaporneuromesh_search_symbolsbefore broad Grep. - Expand only what you need:
neuromesh_expand_foldwith afold_id(orneuromesh_get_file_skeleton/neuromesh_expand_gap). - Use
neuromesh_trace/neuromesh_get_dependencies/neuromesh_analyze_impactfor callers and blast radius. - After a successful edit:
neuromesh_record_feedbackwithtask_successand nodes touched. - If the packet should have changed but
files[]did not, callneuromesh_explain_packet.
Do not treat a utility fallback file as the answer when coverage says seeds missed or packet_gaps is non-empty.
Engine presets (opt-in via nm.config.json)
engine |
When | Agent |
|---|---|---|
fast (default) |
Zero-embed; instant index | Prompt only |
hybrid |
MiniLM sidecar + graph (Phase A Int8) | Prompt only |
deep |
Max quality + dedup + centroids | Prompt only |
| CBM proxy | graph_backend: auto / proxy_cbm |
Conservative proxy claim; native graph for trace/fold |
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.
- yesterday Changed · +17 lines · +139 tokens per session 8b288272d155
- 6d ago First seen · 35 lines · 560 tokens per session scan C 922012c05fca
agent-rule is a cursor rule published in the GitHub repository pinoox/neuromesh (83 stars, last pushed 5d ago), licensed MIT. It adds 699 tokens to every session, about $0.0035 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
cursor-go-skills
Load the Go skills orchestrator before any Go task.
cursorrules
MUST follow the rules in SCALASEMANTICRULES.md for working with Scala code. Mandatory, not optional.
code-indexing-pipeline
How Infigraph turns source into a graph — adding a language (tree-sitter vs ANTLR grammar-plugin), cross-file call resolution, SCIP compiler-grade enrichment, and file-watch/reindex triage.
infigraph
Infigraph architecture, build/test/lint commands, and cross-cutting invariants.
analysis-subsystems
How Infigraph's multi-repo/group mode and taint analysis work internally — HTTP contract extraction heuristics, cross-service edge linking, combined-graph merge, remote mode, plus taint's line-based tracking and sanitizer heuristic.
review-pr-against-issue
Workflow for reviewing a PR against the GitHub issue it claims to fix, including fetching PRs when gh CLI can't reach github.com.