development-workflow

A set of project rules for using pnpm, a JavaScript package manager, and the project’s commands for building, formatting, testing, type-checking, translating, and maintaining agent files.

In plain words
What is it for?
Build and format agents, run validation and locale tests, check TypeScript types, validate or clean translation files, and update the README.
Why use it?
It gives developers the approved commands and explains which checks to run during development.

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/development-workflow
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 774 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.00774
Opus 5 $0.00000 $0.00387
Sonnet 5 $0.00000 $0.00155
Haiku 4.5 $0.00000 $0.00077

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

Security

Grade A, and why

development-workflow 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/development-workflow.mdc · 117 lines

How it starts

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

Development Workflow Guide

This project uses pnpm for package management and has a structured set of scripts for different development tasks.

🔧 NPM Scripts

Core Commands

Located in package.json:

# Build and format agents
pnpm run build          # Build all Agent files
pnpm run format         # Format Agent configurations (triggers translation)

# Validation and testing
pnpm run test           # Run validation tests
pnpm run test:locale    # Test multi-language files
pnpm run type-check     # TypeScript type checking

# Language validation
pnpm run validate:lang              # Validate all translation files
pnpm run validate:lang --delete     # Validate and clean invalid files
pnpm run clean:lang                 # Shorthand for validate with delete

# Maintenance
pnpm run update:awesome             # Update README file

Translation Workflow

The main translation process is triggered by:

pnpm run format

This command:

  1. Calls scripts/commands/format.ts
  2. Executes formatAgents() function
  3. Processes each agent through scripts/formatters/agent-formatter.ts
  4. Performs incremental translation detection
  5. Validates language accuracy
  6. Saves formatted and translated files

🚀 Development Best Practices

Before Making Changes

  1. Run pnpm run type-check to ensure TypeScript correctness
  2. Test changes with a small subset of agents first
  3. Use incremental translation to avoid unnecessary API calls

Code Quality Checks

  • TypeScript: Use strict type checking
  • ESLint: Follow project linting rules
  • Prettier: Code formatting is handled automatically

Testing Translation Changes

# Test specific language
pnpm run test:locale

# Validate a single file
pnpm run validate:lang path/to/agent.en-US.json

# Clean up invalid translations
pnpm run clean:lang

📁 File Structure Patterns

Agent Configuration Files

  • Source files: src/agent-name.json
  • Translations: locales/agent-name/agent-name.locale.json

Read the full file on GitHub · 117 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 · 117 lines · 0 tokens per session scan A 98882d8c4b54

Subscribe to this mod's changes

development-workflow 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 774 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.