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/06-auto-changelog)<a href="https://agentmods.dev/rules/marcoporcellato/matryca-plumber/06-auto-changelog"><img src="https://agentmods.dev/badge/rules/marcoporcellato/matryca-plumber/06-auto-changelog/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/06-auto-changelog"><img src="https://agentmods.dev/badge/rules/marcoporcellato/matryca-plumber/06-auto-changelog.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.00818 | $0.00818 |
| Opus 5 | $0.00409 | $0.00409 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
06-auto-changelog 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 9d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-changelog (standard operating procedure)
At the end of every task or significant modification you complete, update CHANGELOG.md when appropriate. This is mandatory workflow — not optional and not subject to user confirmation.
When to run
Perform this evaluation before proposing a final git commit message or concluding the task (including when the user did not ask for a commit).
Decision gate
Ask: Is this change relevant to the end-user, the system architecture, or another developer using this tool?
| Answer | Action |
|---|---|
| YES | Update CHANGELOG.md under ## [Unreleased] (see below). |
| NO | Do not modify CHANGELOG.md. |
YES — document these
- New features, CLI/MCP/UI surfaces, env vars, or operator-visible behavior (also update
.env.exampleper.cursor/rules/07-env-example.mdc) - Bug fixes that affect runtime, data safety, or integrations
- Performance or reliability improvements users or operators would notice
- Security hardening (SSRF, auth, sandbox, secret handling, rate limits)
- Breaking or behavioral changes to public APIs, config, or graph semantics
- Architecture shifts that change how others extend or deploy the daemon (new modules, bootstrap paths, OpenSpec contracts)
NO — skip the changelog
- Typos, formatting, comments-only edits
- Internal refactors with no observable behavior change
- Test-only changes (unless they document a newly fixed user-visible bug)
- Lockfile-only updates (
uv.lock) unless paired with a dependency change worth calling out - Release chores already captured by
.cursor/rules/05-release-preparation.mdc(version bump, section rename) — do not duplicate bullets
How to update (do this silently)
- Open
CHANGELOG.md. - Under
## [Unreleased], place one concise bullet in the correct subsection:### Added— new capabilities### Changed— behavior or API changes### Fixed— bug fixes### Removed— deprecations or removals### Security— security-only changes (create this heading under[Unreleased]if missing)
- Create the subsection if it does not exist yet under
[Unreleased]. - Match existing style: bold lead — short explanation; optional
`path`or env var; link OpenSpec/docs when relevant. - Do not duplicate an existing bullet; merge into one bullet if the same area was touched again in the same task.
- Do not ask permission to edit the changelog — just do it.
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.
- 9d ago First seen · 72 lines · 818 tokens per session scan A 645d70a8b875
06-auto-changelog is a cursor rule published in the GitHub repository MarcoPorcellato/matryca-plumber (97 stars, last pushed yesterday), licensed Apache-2.0. It adds 818 tokens to every session, about $0.0041 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
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
versioning-and-npm-distribution
Versioning integrity and GitHub/npm distribution flow for AgentProdReady.
branch-dev-main
Always develop on dev; merge to main after verified; keep both in sync.
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.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.