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/08-github-workflow-standards)<a href="https://agentmods.dev/rules/marcoporcellato/matryca-plumber/08-github-workflow-standards"><img src="https://agentmods.dev/badge/rules/marcoporcellato/matryca-plumber/08-github-workflow-standards/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/08-github-workflow-standards"><img src="https://agentmods.dev/badge/rules/marcoporcellato/matryca-plumber/08-github-workflow-standards.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.00021 | $0.01428 |
| Opus 5.5 | $0.00008 | $0.00571 |
| Sonnet 5.5 | $0.00004 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade A, and why
08-github-workflow-standards 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow Standards (Matryca Plumber)
When creating, updating, or closing GitHub issues, pull requests, milestones, or releases, follow these official GitHub best practices so the repository maintains authoritative project management.
Rule routing: Complements 05-release-preparation.mdc (semver releases), 06-auto-changelog.mdc (user-visible bullets), and the user rule for gh pr create.
Issue taxonomy
Title format
Use a category prefix + concise description + optional audit marker:
[Security] Path traversal on read in link verification [v1.9.x Audit #01]
[Bug] Hub pages written without OCC or page_rmw_lock
[Performance] AST cache full-reload on delete or parser failure
[Tech Debt] Centralize _env_bool / _env_int (8+ duplicates)
- Prefix must match the primary label category.
- Audit-track issues include
[v1.9.x Audit #NN]for idempotent bulk scripts.
Body structure (mandatory sections)
Every substantive issue body MUST use these headers (in order):
## Problem Description
## Proposed Architectural Solution
## Estimated Impact
## Files Involved
Add metadata footer when from audit or epic:
---
**Audit metadata** / **Epic link**
_Closes when merged with tests green (`make check`) and CHANGELOG updated._
Labels (semantic, lowercase)
| Label | When to use |
|---|---|
security |
Sandbox, auth, secret handling, SSRF |
bug |
Incorrect behavior, race, data loss |
performance |
I/O, memory, latency |
tech-debt |
Refactor, DRY, typing, module split |
v1.9.x |
Pre-v2.0 perfection track |
v2.0 |
Shadow DB / Safe-Sync epic |
v2-prep |
Phase 0–1: prerequisites, GraphRepository ports |
v2-alpha |
Phase 2–3: shadow sync, read routing flag |
v2-memory |
Biological memory layer |
v2-safesync |
Logseq DB Safe-Sync write bridge |
audit-2026 |
Bulk-created from perfection audit |
Create missing labels via gh label create before assigning. Use scripts/github_audit_tracker.sh as the canonical bulk importer.
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 · 164 lines · 21 tokens per session scan A 168987ec3578
08-github-workflow-standards is a cursor rule published in the GitHub repository MarcoPorcellato/matryca-plumber (100 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 1,428 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
aionforge-memory
Aionforge Memory cadence and vocabulary — recall first, capture as you go, track tasks as work items.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.
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.