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/extralabs/octowatch-mcp-serverWrote 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/extralabs/octowatch-mcp-server/oss-boundary)<a href="https://agentmods.dev/rules/extralabs/octowatch-mcp-server/oss-boundary"><img src="https://agentmods.dev/badge/rules/extralabs/octowatch-mcp-server/oss-boundary.svg" alt="Measured on agentmods" 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.00330 | $0.00330 |
| Opus 5 | $0.00165 | $0.00165 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
oss-boundary 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 6d 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
Public OSS safety (octowatch-mcp-server)
This repository is public open source. Anything committed or pasted into docs/examples/code here can be published.
Private sibling code (reference only)
The maintainer may have local private frontend/backend checkouts. Use them only to discover public API contracts, request shapes, and field names.
Do not:
- Commit absolute local disk paths to those private repos
- Vend, paste, or rewrite large chunks of their source into this repo
- Document internal module layouts beyond what is needed for the public REST client
Never put in this repo
- Production passwords, tokens, connection strings, private keys, certs, cloud keys
- Non-public internal hosts (documented Cloud API host is OK)
- Full proprietary modules, controllers, business rules, licensing, billing, OCR pipelines
- Customer data dumps or raw monitoring payloads from non-demo tenants
Allowed
- Public demo credentials (
[email protected]/demo) with clear warnings - Documented REST paths, headers, and JSON shapes needed for the MCP client
- Minimal original OSS code that calls the public API
- High-level notes in
docs/that describe behavior, not internal implementation
When in doubt
Prefer re-deriving from live public Help/API docs and demo responses. If a change would only make sense with private backend knowledge that competitors could abuse, leave it out or ask the user.
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.
- 6d ago First seen · 37 lines · 330 tokens per session scan A 7b1126d76c10
oss-boundary is a cursor rule published in the GitHub repository extralabs/octowatch-mcp-server (2 stars, last pushed 10d ago), licensed MIT. It adds 330 tokens to every session, about $0.0016 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.
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.
cli-error-handling
CLI command error handling patterns.
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.