scripts-architecture

A set of project rules for keeping scripts in separate folders by role, such as core settings, utilities, parsing, processing, validation, and building.

In plain words
What is it for?
Use it as a structure guide when adding or reviewing scripts, including parsers, validators, processors, builders, and shared utilities.
Why use it?
It makes the codebase easier to navigate and helps prevent unrelated script responsibilities from being mixed together.

Cursor rule for Cursor

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/x402agent/solana-clawd/scripts-architecture
Clone the repo
git clone --depth 1 https://github.com/x402agent/solana-clawd

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 936 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00936
Opus 5 $0.00000 $0.00468
Sonnet 5 $0.00000 $0.00187
Haiku 4.5 $0.00000 $0.00094

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

Security

Grade A, and why

scripts-architecture 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/.cursor/rules/scripts-architecture.mdc · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scripts Directory Architecture Guide

This project uses a modular scripts directory structure for maintainability and clear separation of concerns.

📁 Directory Structure

Core Module (scripts/core/)

Utility Modules (scripts/utils/)

Processing Modules

Validation Modules

Build System

Command Line Tools (scripts/commands/)

Read the full file on GitHub · 85 lines

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 · 85 lines · 0 tokens per session scan A 350310c87754

Subscribe to this mod's changes

scripts-architecture is a cursor rule published in the GitHub repository x402agent/solana-clawd (24 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 936 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.