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/terryso/mcp-pinterestWrote 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/terryso/mcp-pinterest/rule-update-cursor-modes-manual)<a href="https://agentmods.dev/rules/terryso/mcp-pinterest/rule-update-cursor-modes-manual"><img src="https://agentmods.dev/badge/rules/terryso/mcp-pinterest/rule-update-cursor-modes-manual/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/terryso/mcp-pinterest/rule-update-cursor-modes-manual"><img src="https://agentmods.dev/badge/rules/terryso/mcp-pinterest/rule-update-cursor-modes-manual.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.00000 | $0.00809 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
rule-update-cursor-modes-manual 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 9d 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- rule-update-cursor-modes-manual — 100% identical, 0 lines differ
- rule-update-cursor-modes-manual — 100% identical, 0 lines differ
- rule-update-cursor-modes-manual — 100% identical, 0 lines differ
- rule-update-cursor-modes-manual — 100% identical, 0 lines differ
- rule-update-cursor-modes-manual — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Mode Update Agent
Context
- Apply this rule when the user asks to create a new agent/character for Cursor or modify an existing one
- This rule provides guidance for adding or updating entries in the .cursor/modes.json file
- Follows the format specified in .cursor/templates/mode-format.md
Critical Rules
- Read the current .cursor/modes.json file to understand existing modes
- Read .cursor/templates/mode-format.md to ensure compliance with the schema
- When creating a new agent, ask for:
- Agent name (short CapCase format for tab display)
- Full description (character name and role)
- Persona details (speaking style, character traits)
- Model selection
- Tool access requirements
- Auto behavior preferences
- When updating an existing agent, ask which specific attributes need modification
- Add Star Trek themed personality traits that fit the character's role
- Ensure the customPrompt contains guidance on file access restrictions
- Validate that model names match those in the supported models list
- Always update both modes.json and also add or update the character in docs/custom-agents.md
- Follow the standard format in docs/custom-agents.md for consistency
Examples
AI: I'll help you create a new Cursor agent based on Lwaxana Troi. Let me first check the current modes.json and format requirements.
[AI reads .cursor/modes.json and .cursor/templates/mode-format.md]
Here's what I propose for this new agent:
Name: LwaxanaUX Description: UX Designer - Lwaxana Troi Model: claude-3.7-sonnet Persona: Flamboyant, theatrical, outspoken, and telepathically intuitive about user needs
Would you like me to proceed with adding this agent? I'll need to update both the modes.json file and the custom-agents.md documentation.
User: Yes, please add her with access to all cursor tools and Tavily for research.
[AI updates both .cursor/modes.json and docs/custom-agents.md with the new agent]
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.
- 9d ago First seen · 82 lines · 0 tokens per session scan A 9b569f1e5009
rule-update-cursor-modes-manual is a cursor rule published in the GitHub repository terryso/mcp-pinterest (37 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 809 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
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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.