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/ctxr-dev/llm-wiki-memoryWrote 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/ctxr-dev/llm-wiki-memory/release-migrations-authoring)<a href="https://agentmods.dev/rules/ctxr-dev/llm-wiki-memory/release-migrations-authoring"><img src="https://agentmods.dev/badge/rules/ctxr-dev/llm-wiki-memory/release-migrations-authoring/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/ctxr-dev/llm-wiki-memory/release-migrations-authoring"><img src="https://agentmods.dev/badge/rules/ctxr-dev/llm-wiki-memory/release-migrations-authoring.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.00080 | $0.00080 |
| Opus 5.5 | $0.00032 | $0.00032 |
| Sonnet 5.5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
release-migrations-authoring 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
Follow the canonical rule (edit that file, never this shadow):
@.agents/rules/release-migrations-authoring.md
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 · 9 lines · 80 tokens per session scan A b3c6d2f0424f
release-migrations-authoring is a cursor rule published in the GitHub repository ctxr-dev/llm-wiki-memory (129 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session, about $0.0003 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
08-github-workflow-standards
GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).
06-auto-changelog
Always keep the CHANGELOG updated with meaningful changes.
05-release-preparation
Prepare a semver release (CHANGELOG, pyproject.toml, uv.lock, checks).
github-cli
Apply when using the gh CLI to manage pull requests, issues, releases, or CI workflows on GitHub.
changesets
Changeset format and bump rules enforced by CI.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.