agentmods.dev

code-organization

A set of rules for organizing files under a project’s src/ folder. It separates reusable helpers from modules tied to a particular service, API, smart contract, or business domain.

In plain words
What is it for?
Use it when adding or moving TypeScript files: put stateless helpers and shared infrastructure in src/utils/, and external integrations or domain modules in src/services/. Larger services can be grouped into subfolders.
Why use it?
It makes it easier to know where new code belongs and keeps general utilities independent from domain-specific code. This supports simpler reuse and isolated testing of generic helpers.

Cursor rule for Cursor

5 13d ago A scan 390 tokens original MIT
View the source file vechain/vechain-mcp-server
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/vechain/vechain-mcp-server/code-organization
Clone the repo
git clone --depth 1 https://github.com/vechain/vechain-mcp-server

Made for: Cursor.

Per session 390 This file is loaded in full into every session.
When invoked 390 The same file — it is already loaded in full.
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.00390 $0.00390
Opus 5 $0.00195 $0.00195
Sonnet 5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

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

Security

Grade A, and why

code-organization 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/code-organization.mdc · 44 lines

What it actually says

Code Organization

Keep src/ organized by purpose. Place new files in the correct folder.

src/utils/

Generic, stateless helpers with no domain knowledge. Reusable across the codebase and easy to unit-test in isolation.

Examples: fetch.ts, logger.ts, concurrency.ts.

Put here:

  • Pure functions and small helpers (formatting, parsing, retries, batching, concurrency primitives)
  • Cross-cutting infrastructure (logger, generic HTTP wrappers)
  • Anything that does NOT depend on a specific VeChain/VeBetterDAO domain concept

src/services/

Domain-specific modules that integrate with an external system, contract, API, or business concept. May hold configuration, clients, or stateful wrappers.

Examples: vebetterdao-contracts.ts, ipfs.ts, vns.ts, price-oracle.ts, thor/, token-registry/, validator-hub/.

Put here:

  • Smart contract clients and ABIs wrappers
  • API clients for a specific service (IPFS, indexers, oracles, registries)
  • Anything tied to a domain concept (VNS, B3TR, VeBetterDAO apps, Thor node)

If a service grows, promote it to a subfolder (e.g. services/thor/).

Quick decision

  • "Could this live in any TypeScript project unchanged?" -> utils/
  • "Does this know about VeChain, a contract, or an external API?" -> services/

Do not

  • Do NOT place helpers next to tools/ or at the root of src/
  • Do NOT mix domain logic into utils/
  • Do NOT duplicate helpers — check utils/ and services/ first before adding a new file
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 · 44 lines · 390 tokens per session scan A d645d1c53b2c

Subscribe to this mod's changes

code-organization is a cursor rule published in the GitHub repository vechain/vechain-mcp-server (5 stars, last pushed 13d ago), licensed MIT. It adds 390 tokens to every session, about $0.0019 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.

Backend and APIsLanguages
Related

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.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

typescript

Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.

streamlit/streamlit · 4,669 tokens

coolify-ai-docs

Master reference to all Coolify AI documentation in .ai/ directory.

coollabsio/coolify · 1,426 tokens

python_lib

Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.

streamlit/streamlit · 0 tokens

specs

This directory contains product and tech specs for Streamlit features.

streamlit/streamlit · 0 tokens