export-test-plugin

A set of ContextOS rules for an export-test-plugin, containing a skill name and a unique test marker.

In plain words
What is it for?
It is intended for testing plugin export and installation context.
Why use it?
The available information does not explain any broader behavior.

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/kok-o/koko-contextos-agents/export-test-plugin
Clone the repo
git clone --depth 1 https://github.com/kok-o/koko-contextos-agents

Made for: Cursor.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 41 The whole file, excluding the scripts and references it only reads on demand.
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.00007 $0.00041
Opus 5 $0.00003 $0.00020
Sonnet 5 $0.00001 $0.00008
Haiku 4.5 $0.00001 $0.00004

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

Security

Grade A, and why

export-test-plugin 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.

.cursor/rules/export-test-plugin.mdc · 13 lines

What it actually says

Skill: export-test-plugin

Export test plugin

Plugin instructions unique-marker-export-test.

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 · 13 lines · 7 tokens per session scan A 421d1a12f028

Subscribe to this mod's changes

export-test-plugin is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 3d ago), licensed MIT. It adds 7 tokens to every session and 41 once invoked, about $0.0000 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.

Related

Other cursor rules, from other repositories

clean-code

Apply language-agnostic clean-code discipline to all code writing, editing, reviewing, testing, and refactoring, including file placement, single responsibility, and verified completion.

btseee/clean-code-skills · 1,307 tokens

unity-performance

Cursor rule "unity-performance" from Common-ka/ai-agent-unity-rules, covering unity performance rules, update/fixedupdate/lateupdate, usage rules, object pooling (unityengine.pool) and addressables (not resources).

Common-ka/ai-agent-unity-rules · 2 tokens

react-composition-patterns

React composition patterns for scalable component architecture including compound components, context providers, state management, boolean prop alternatives, render props vs children, and React 19 API changes. Use when refactoring components with many boolean props, building component libraries, designing flexible…

alonsarias/agent-rules · 0 tokens

react-advanced-patterns

Advanced React patterns for refs, stable callbacks, useEffectEvent, and application initialization. Use when dealing with event handler refs, stable callback references, subscription management, effect dependencies, or one-time app initialization.

alonsarias/agent-rules · 0 tokens

general-typescript-rule

Applies general TypeScript best practices and style guidelines to all TypeScript files in the project.

yujiosaka/knowhub · 0 tokens

readme-best-practices

README Best Practices - enforces high-quality README patterns when creating or editing README files.

ofershap/readme-best-practices · 276 tokens