roslyn-mcp-docs-lifecycle

roslyn-mcp-docs-lifecycle is a cursor rule for Cursor from VuDZ/RoslynMcpServer. It costs 286 tokens per session, scanned A, original, MIT.

A document-management process for technical specifications. It explains where to keep active specifications, review material, and completed design history.

In plain words
What is it for?
Use it when starting or closing a documentation specification, especially when moving review files to an archive or updating the documentation index.
Why use it?
It prevents old reviews and draft copies from being mistaken for the current specification. It also keeps finished documentation discoverable without changing the accepted design.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when starting or closing a documentation specification, especially when moving review files to an archive or updating the documentation index.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/vudz/roslynmcpserver/roslyn-mcp-docs-lifecycle
Install

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.

Clone the repo
git clone --depth 1 https://github.com/VuDZ/RoslynMcpServer

Made for: Cursor.

Wrote 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.

agentmods badge for roslyn-mcp-docs-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-docs-lifecycle/github.svg)](https://agentmods.dev/rules/vudz/roslynmcpserver/roslyn-mcp-docs-lifecycle)
Your own site
<a href="https://agentmods.dev/rules/vudz/roslynmcpserver/roslyn-mcp-docs-lifecycle"><img src="https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-docs-lifecycle/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.

agentmods 80×15 button for roslyn-mcp-docs-lifecycle

Your own site · 80×15
<a href="https://agentmods.dev/rules/vudz/roslynmcpserver/roslyn-mcp-docs-lifecycle"><img src="https://agentmods.dev/badge/rules/vudz/roslynmcpserver/roslyn-mcp-docs-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 286 This file is loaded in full into every session.
When invoked 286 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00286 $0.00286
Opus 5 $0.00143 $0.00143
Sonnet 5 $0.00057 $0.00057
Haiku 4.5 $0.00029 $0.00029

Measured 2d ago against content hash 5bf075cb3ac8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-16, from the pricing page.

Security

Grade A, and why

roslyn-mcp-docs-lifecycle 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 2d 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.

.cursor/rules/roslyn-mcp-docs-lifecycle.mdc · 25 lines

What it actually says

Docs spec lifecycle

Index: docs/README.md. Canon vs process: _archive/ inside the topic; closed series without contract → docs/archive/.

Starting a spec

Before implementing or editing docs/<topic>/:

  • Look next to the canon for leftover process: review/, review-response/, arbitration/, or pre-arb epoch copies with the same names as the live spec.
  • If any sit on the live shelf, propose moving them to <topic>/_archive/ first. Do not treat review as the spec. Do not move silently.

Closing a series

When every epoch is accepted/shipped and UNRESOLVED / U-ARB gates for that series are closed or explicitly skipped, remind the user to archive:

  • Still cited from ARCHITECTURE / product README as live contract → keep in docs/; archive only process.
  • History only (no remaining contract) → docs/archive/<topic>/ and update the tables in docs/README.md.

Do not delete accepted/rejected review. Do not rewrite specs “to match reality” after ship — copy facts into ARCHITECTURE / README and mark the design shipped.

Changes

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.

  1. 2d ago First seen · 25 lines · 286 tokens per session scan A 5bf075cb3ac8

Subscribe to this mod's changes

roslyn-mcp-docs-lifecycle is a cursor rule published in the GitHub repository VuDZ/RoslynMcpServer (7 stars, last pushed yesterday), licensed MIT. It adds 286 tokens to every session, about $0.0014 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-09-14.