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/swonvip/mcp-server-talk/repository-restructuring-plangit clone --depth 1 https://github.com/SwonVIP/mcp-server-talkWrote 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/swonvip/mcp-server-talk/repository-restructuring-plan)<a href="https://agentmods.dev/rules/swonvip/mcp-server-talk/repository-restructuring-plan"><img src="https://agentmods.dev/badge/rules/swonvip/mcp-server-talk/repository-restructuring-plan.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.00000 | $0.00541 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
repository-restructuring-plan 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Restructuring Plan
Overview
Restructuring the repository to separate presentation content from demo materials and maintain functionality.
Current Structure
├── index.html # Main presentation file
├── deck/ # Presentation assets (images)
├── lib/ # Reveal.js dependencies
├── css/ # Stylesheets
├── js/ # JavaScript files
├── presentation-content.md # Content planning document
├── package.json # Node.js dependencies
├── gulpfile.js # Build configuration
└── other reveal.js files...
Target Structure
├── presentation/
│ ├── index.html # Main presentation file
│ ├── deck/ # Presentation assets
│ ├── lib/ # Reveal.js dependencies
│ ├── css/ # Stylesheets
│ ├── js/ # JavaScript files
│ ├── package.json # Node.js dependencies
│ ├── gulpfile.js # Build configuration
│ └── presentation-content.md
├── demo/
│ └── (empty for now, ready for demo content)
└── README.md (updated)
Implementation Steps
- Create
/presentationdirectory - Move all presentation-related files to
/presentation - Create empty
/demodirectory for future use - Update paths in presentation files to work from new location
- Update package.json scripts if needed
- Test that presentation still works when run from
/presentationfolder - Update README.md with new structure information
Files to Move
- index.html → presentation/index.html
- deck/ → presentation/deck/
- lib/ → presentation/lib/
- css/ → presentation/css/
- js/ → presentation/js/
- package.json → presentation/package.json
- package-lock.json → presentation/package-lock.json
- gulpfile.js → presentation/gulpfile.js
- presentation-content.md → presentation/presentation-content.md
- node_modules/ → presentation/node_modules/
- dist/ → presentation/dist/
- plugin/ → presentation/plugin/
- examples/ → presentation/examples/
- test/ → presentation/test/
- reveal.js/ → presentation/reveal.js/
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.
- 4d ago First seen · 77 lines · 0 tokens per session scan A 980c7cbea7e8
repository-restructuring-plan is a cursor rule published in the GitHub repository SwonVIP/mcp-server-talk (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 541 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-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-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.