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/TraceOrb/obs-mcpWrote 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/traceorb/obs-mcp/index)<a href="https://agentmods.dev/rules/traceorb/obs-mcp/index"><img src="https://agentmods.dev/badge/rules/traceorb/obs-mcp/index/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/traceorb/obs-mcp/index"><img src="https://agentmods.dev/badge/rules/traceorb/obs-mcp/index.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.00429 | $0.00429 |
| Opus 5.5 | $0.00172 | $0.00172 |
| Sonnet 5.5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
index 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
Rule index (mandatory)
.cursor/rules/ and .claude/rules/ contain only this file. Every other rule lives in obs-docs. Do not look for rules under these folders besides the index. Do not copy rules into .ai-rules/.
The Cursor workspace is the parent folder observability. Read with that path. If this repo is open alone, prefix with ../.
Before writing or changing code: Read the always-on files below. Then, if the task matches a row, Read that file too. Do not Read the rest.
Always — Read these now (every task)
| File | What it enforces |
|---|---|
obs-docs/05-architecture/dev/rules/code-style-rules.md |
Mappers, no comments, no ternary, no else |
obs-docs/05-architecture/dev/rules/typing-rules.md |
Strict TS, no any, no as, closed Record |
obs-docs/05-architecture/dev/rules/testing-rules.md |
Spec for new or changed behavior |
obs-docs/05-architecture/dev/rules/commit-rules.md |
Conventional Commits; agent commits, person publishes |
obs-docs/05-architecture/dev/rules/security-rules.md |
Org isolation; read key only reads; MCP never sees ClickHouse |
On demand — Read only if the task matches
| When you are… | Read |
|---|---|
| Adding or changing an MCP tool | obs-docs/docs/superpowers/specs/2026-08-22-read-key-mcp-design.md |
| Publishing the package or changing CI | obs-docs/05-architecture/dev/rules/deployment-rules.md |
If two on-demand rows match, Read both. If none match, stop after the always-on files.
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 · 32 lines · 429 tokens per session scan A 762d0bdae7f9
index is a cursor rule published in the GitHub repository TraceOrb/obs-mcp (1 stars, last pushed 26d ago), licensed MIT. It adds 429 tokens to every session, about $0.0017 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.