agentmods.dev

mcp-session-logging

A set of rules requiring an MCP session log before and after work. MCP, or Model Context Protocol, is a way for an agent to use connected tools and services.

In plain words
What is it for?
Use it in projects that require session auditing, server health checks, task tracking, and a final record of actions and changed files.
Why use it?
It creates a record of the session and checks the server, recent history, and current tasks before work begins. This is intended to prevent work from proceeding without the required workspace context.

Cursor rule for Cursor

2 11d ago A scan 280 tokens original Apache-2.0
View the source file sharpninja/McpServer
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.

agentmods
npx agentmods add rules/sharpninja/mcpserver/mcp-session-logging
Clone the repo
git clone --depth 1 https://github.com/sharpninja/McpServer

Made for: Cursor.

Per session 280 This file is loaded in full into every session.
When invoked 280 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00280 $0.00280
Opus 5 $0.00140 $0.00140
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

Measured yesterday against content hash 777338266175, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-session-logging 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 yesterday.

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/mcp-session-logging.mdc · 28 lines

What it actually says

MCP Session Logging — Mandatory Precondition

⚠️ PRIORITY ORDER — NON-NEGOTIABLE ⚠️

Speed is never more important than following workspace procedures.

Before doing ANY work on ANY user request, you MUST complete these steps in order:

  1. Read AGENTS-README-FIRST.yaml in the repo root for the current API key and endpoints
  2. GET /health to verify the MCP server is running
  3. POST /mcp/sessionlog with your session entry — do NOT proceed until this succeeds
  4. GET /mcp/sessionlog?limit=5 to review recent session history for context
  5. GET /mcp/todo to check current tasks
  6. THEN begin working on the user's request

On EVERY subsequent user message:

  1. POST an updated session log entry BEFORE starting work
  2. Complete the user's request
  3. POST the final session log with results, actions taken, and files modified

If you skip any of these steps, STOP and go back and do them before continuing. Session logging is not optional, not deferred, and not secondary to the task. Failure to maintain the session log is a compliance violation.

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. yesterday First seen · 28 lines · 280 tokens per session scan A 777338266175

Subscribe to this mod's changes

mcp-session-logging is a cursor rule published in the GitHub repository sharpninja/McpServer (2 stars, last pushed 11d ago), licensed Apache-2.0. It adds 280 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-08-31.

Data and AIPlanningai-agentsai-mcpai-tools
Related

Other cursor rules, from other repositories

cursor

You are working on the checkout service. Preserve transaction integrity and auditability.

mrwogu/promptscript · 53 tokens

java-springboot-jpa-cursorrules-prompt-file

description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.

ItamarZand88/awesome-agent-conventions · 1,052 tokens

002-verify-before-act

Requires Claude to read before writing, verify before installing, and confirm before destructive operations.

bookedsolidtech/helixir · 306 tokens

swift-development

Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.

madebyaris/rakitui-ai · 0 tokens

design-patterns

Design patterns (GoF) and file size conventions for sweagent TypeScript codebase.

sijeeshmiziha/visionagent · 894 tokens

database

Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.

ItamarZand88/awesome-agent-conventions · 444 tokens