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/vechain/vechain-mcp-serverWrote 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/vechain/vechain-mcp-server/code-organization)<a href="https://agentmods.dev/rules/vechain/vechain-mcp-server/code-organization"><img src="https://agentmods.dev/badge/rules/vechain/vechain-mcp-server/code-organization/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/vechain/vechain-mcp-server/code-organization"><img src="https://agentmods.dev/badge/rules/vechain/vechain-mcp-server/code-organization.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.00390 | $0.00390 |
| Opus 5.5 | $0.00156 | $0.00156 |
| Sonnet 5.5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
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 1mo 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
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 ofsrc/ - Do NOT mix domain logic into
utils/ - Do NOT duplicate helpers — check
utils/andservices/first before adding a new file
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.
- 1mo ago First seen · 44 lines · 390 tokens per session scan A d645d1c53b2c
code-organization is a cursor rule published in the GitHub repository vechain/vechain-mcp-server (5 stars, last pushed 2d ago), licensed MIT. It adds 390 tokens to every session, about $0.0016 per session on Opus 5.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.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).