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.
git 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/03-logseq-api)<a href="https://agentmods.dev/rules/marcoporcellato/matryca-plumber/03-logseq-api"><img src="https://agentmods.dev/badge/rules/marcoporcellato/matryca-plumber/03-logseq-api/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.
<a href="https://agentmods.dev/rules/marcoporcellato/matryca-plumber/03-logseq-api"><img src="https://agentmods.dev/badge/rules/marcoporcellato/matryca-plumber/03-logseq-api.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00213 |
| Opus 5.5 | $0.00000 | $0.00085 |
| Sonnet 5.5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
03-logseq-api 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.
What it actually says
Direct File I/O (The Plumber Way)
- Most operations in Matryca Plumber are performed by directly reading/writing the local
.mdfiles in the graph directory. - Never use the HTTP API for background linting, semantic indexing, or graph analysis. Rely on the local file system using proper parsing, UTF-8 encoding, and optimistic concurrency (mtime checks).
The Local HTTP API (Future/Active Agent Bridge)
- If building live interactive tools (e.g., MCP endpoints) that require Logseq to be running, use the Local HTTP API:
http://localhost:12315. - Authentication: send the token as a Bearer token in the
Authorizationheader. - Protocol: Requests use JSON-RPC-shaped payloads over HTTP.
- Favor Direct File I/O unless real-time UI manipulation inside Logseq is strictly required.
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 · 14 lines · 0 tokens per session scan A 2c5b70ebdd2c
03-logseq-api is a cursor rule published in the GitHub repository MarcoPorcellato/matryca-plumber (100 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 213 tokens. 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.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.