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.
npx agentmods add rules/langfuse/langfuse-docs/changelog-postsgit clone --depth 1 https://github.com/langfuse/langfuse-docsWhat 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 | $0.00000 | $0.00662 |
| Opus 5 | $0.00000 | $0.00331 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
changelog-posts 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Posts Guidelines
Overview
Changelog posts document updates, new features, bug fixes, and improvements. They serve as a historical record of changes and provide clarity for users and developers alike.
File Placement
- Place all changelog posts in the
/content/changelogdirectory. - Use a clear naming convention (e.g., include the date and a brief description, such as
2023-10-01-new-feature.md). - Please make sure you use today's date. If unsure, use terminal to get today's date.
Frontmatter Configuration Options
Each changelog post should define the following frontmatter fields:
-
title (string, required): The title of the changelog entry, displayed prominently in both the header and index.
-
description (string, required): A concise summary of the changes covered in the post.
-
date (string, required): The release date of the update. Use a date format that can be parsed by JavaScript (e.g., YYYY-MM-DD). This is formatted and displayed in the changelog header and index.
-
author (string, required): The name or identifier of the author responsible for the changelog entry.
-
showOgInHeader (boolean, optional): Set to false to hide the media in the header. If omitted or true, media will be rendered as described below.
-
ogVideo (string, optional): mp4 file url for video, needs to be 16:9. Usually hosted on https://static.langfuse.com/docs-videos (cloudflare r2 bucket).
-
ogImage (string, optional): The URL of an image to display if there is no video. If both an image and a GIF are provided, the GIF may be prioritized.
-
gif (string, optional): URL for an animated GIF. This can be used in place of a static image if desired.
Note: The display components (ChangelogHeader.tsx and ChangelogIndex.tsx) use these options in the following priority order:
- Fallback Video (
ogVideo) - Image (
ogImage), optionally replaced bygifif provided
Content Structure
- After the frontmatter
- Never forget to add the
ChangelogHeadercomponent after the frontmatter.
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.
- 2d ago First seen · 76 lines · 0 tokens per session scan A 854556391bca
changelog-posts is a cursor rule published in the GitHub repository langfuse/langfuse-docs (237 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 662 tokens. 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
mcp-framework
We are in the mcp-framework , a typescript framework that allows construction of model context protocol (mcp) servers. We are implementing the new specification: Overview MCP provides a standardized way for applications to.
langfuse-mcp-general-rules
Cursor rule "langfuse-mcp-general-rules" from avivsinai/langfuse-mcp, covering building and publishing to pypi, version numbering and tagging and build and publish workflow.
jawn
Cursor rule "jawn" from Helicone/helicone, covering helicone jawn controller and tanstack query integration, controller pattern, manager pattern, frontend hooks with tanstack query and type definitions.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
architecture
agent-inspect architecture and product context.
nodejs
This guide will walk you through installing Node.js using NVM (Node Version Manager) and setting up pnpm as your package manager.