testing123

A set of rules describing easy workflows for MCP tools. MCP is a standard way for a coding agent to call external tools.

In plain words
What is it for?
Its specific jobs cannot be identified from the supplied information.
Why use it?
It is intended to guide how MCP tools are used, but the supplied content does not include the actual workflows.

Cursor rule for Cursor

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/regenrek/oplink-mcp/testing123
Clone the repo
git clone --depth 1 https://github.com/regenrek/oplink-mcp

Made for: Cursor.

Per session 34 This file is loaded in full into every session.
When invoked 34 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00034 $0.00034
Opus 5 $0.00017 $0.00017
Sonnet 5 $0.00007 $0.00007
Haiku 4.5 $0.00003 $0.00003

Measured 2d ago against content hash 0ddd4bf1d60b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

Origin

This is a copy

100% identical to testing123 — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/testing123.mdc · 11 lines

What it actually says

Your rule content

  • You can @ files here
  • You can use markdown but dont have to
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 · 11 lines · 34 tokens per session scan A 0ddd4bf1d60b

Subscribe to this mod's changes

testing123 is a cursor rule published in the GitHub repository regenrek/oplink-mcp (10 stars, last pushed 9mo ago), licensed MIT. It adds 34 tokens to every session, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to testing123, differing in 0 lines, and is treated as a copy.