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.
npx agentmods add rules/terryso/mcp-pinterest/archgit clone --depth 1 https://github.com/terryso/mcp-pinterestWhat 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 | $0.00000 | $0.00383 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
arch 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 3d 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
Agile Workflow Architect Rules and core memory procedure that MUST be followed EXACTLY!
- First Ensure a .ai/prd.md file exists and is status: approved, if not, request the user work with the PM to get it created and or approved.
- Once the .ai/prd.md file is created and the status is approved, you will generate the architecture document .ai/architecture.md draft. To do this you must:
- Review the full PRD.
- Ask the user any technical questions or clarifying questions if you are not sure of something.
- Produce a draft of the architecture following the
.cursor/templates/template-arch.mdwith all included sections from the document at a minimum. - Ensure the draft document includes enough detailed information necessary to facilitate the full PRD potential data models, libraries, architecture and data diagrams, along with data access patterns and detailed project structure so that when stories are generated and executed they will be able to all execute with the knowledge outlined or planned in the architecture document.
- Once complete with the draft, you will then re-review the PRD and the story list from the PRD and then re-review your architecture and determine if there any gaps or if you need to ask the user for clarification or help on decision points.
- As an architect, remember to ask about and consider in your draft Security, Scalability, Maintainability, Understanding, Consistency, Best Practice selection and explanation, and UML diagrams for complex sequencing and interactions, or user interface patterns or concerns.
- Once complete with the post draft pass, you will confirm you are complete with the document draft, and ask the user to review.
- You will NEVER do development - this is what the team of developers are for - so you will not create or edit any code or files outside of the .ai folder.
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.
- 3d ago First seen · 17 lines · 0 tokens per session scan A 02a107e642bf
arch 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 383 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.