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/marcoporcellato/matryca-plumber/01-core-paradigmgit clone --depth 1 https://github.com/MarcoPorcellato/matryca-plumberWrote 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/marcoporcellato/matryca-plumber/01-core-paradigm)<a href="https://agentmods.dev/rules/marcoporcellato/matryca-plumber/01-core-paradigm"><img src="https://agentmods.dev/badge/rules/marcoporcellato/matryca-plumber/01-core-paradigm.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.00511 | $0.00511 |
| Opus 5 | $0.00255 | $0.00255 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
01-core-paradigm 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 6d 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.
What it actually says
Project context
This repository builds Matryca Plumber, a local-first, background AI daemon and engine that operates directly on Logseq OG (local, pure Markdown graph notes) file systems.
SSOT: full paradigm spec lives in docs/openspec/agent/paradigm.md. Pointer: docs/openspec/logseq-paradigm.md. This rule is the Cursor summary only.
Outliner paradigm (non-negotiable)
- Logseq OG uses pure Markdown files. The atomic unit is the block: an indented bullet point that forms a tree, not a flat document body.
- When generating or editing content, produce hierarchical outliner text (nested bullets).
- Bulleted Headings: AI-generated sections must use
- ### Heading Titleto ensure they are foldable in the Logseq outliner. - Co-working assumption: Humans and the daemon edit the same
.mdfiles concurrently. Favor diffs that preserve indentation, block order, andid::lines.
Properties Rules (CRITICAL)
- Block Properties: Must be placed immediately after the bullet text, before any indented children. They must be indented by exactly 2 spaces relative to the parent bullet (e.g.,
id:: <uuid>,matryca-plumber:: true). NEVER orphan or delete existing block properties. - Page Properties: Must reside in the Absolute Frontmatter at the top of the file (Line 0). They are raw text
key:: valuelines WITHOUT bullet dashes (-), separated by a blank line before the first bullet. - Lists:
alias::andtags::are comma-separated lists. Do not duplicate keys. Strip markdown (#,[[ ]]) from their values.
File System & Namespaces
- Semantic vs Physical: In memory/content, use
/(e.g.,[[Domain/Subdomain]]). On disk, use Logseq's encoding: replace/with___and URL-encode reserved OS characters (e.g.,?->%3F). - Encoding: ALL file read/write operations must strictly use
encoding="utf-8".
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.
- 6d ago First seen · 24 lines · 511 tokens per session scan A 8b51a41f4ae6
01-core-paradigm is a cursor rule published in the GitHub repository MarcoPorcellato/matryca-plumber (96 stars, last pushed today), licensed Apache-2.0. It adds 511 tokens to every session, about $0.0026 per session on Opus 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-30.
Other cursor rules, from other repositories
aionforge-memory
Aionforge Memory cadence and vocabulary — recall first, capture as you go, track tasks as work items.
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
open-dynamic-workflows
Route workflow, ultracode, and deep-research requests through Open Dynamic Workflows.
stock-data
Stock data domain (TW/US markets, FinMind, Massive, ticker insights, charts, translations). Auto-attached when editing stock-related code.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.