What is development_workflow?

A set of development rules for Spamoor, a Go tool that sends Ethereum transactions for testing. It documents build commands, local development, tests, documentation, and Git conventions.

Use it when setting up Spamoor, compiling its binaries, generating API documentation, running tests, using a local Ethereum test network, or preparing changes.

It gives contributors one reference for building and testing the project. It reduces uncertainty about required settings and the expected development workflow.

development_workflow — Cursor rule by ethpandaops

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/ethpandaops/spamoor/development_workflow

Clone the repo

git clone --depth 1 https://github.com/ethpandaops/spamoor

Made for: Cursor.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 967 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.

Model	Per session	Once invoked
Fable 5	$0.00007	$0.00967
Opus 5	$0.00003	$0.00483
Sonnet 5	$0.00001	$0.00193
Haiku 4.5	$0.00001	$0.00097

Measured yesterday against content hash aaef510c2d84, 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 yesterday.

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/development_workflow.mdc · 178 lines

How it starts

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

Spamoor Development Workflow

Build System

Makefile Targets

make all: Build documentation and binaries
make build: Build binaries with optimizations
make build-lib: Build using library mode (without replace directive)
make docs: Generate Swagger API documentation
make test: Run all tests
make clean: Clean build artifacts

Build Configuration

CGO_ENABLED=1: Required for SQLite and cryptographic operations
Build tags: Use with_blob_v1,ckzg for blob transaction support
Optimization flags: -s -w for stripped binaries
Version injection: Git commit hash and build time embedded

Development Environment

Local Development

# Standard development setup
git clone https://github.com/ethpandaops/spamoor.git
cd spamoor
make all

# Run tests
make test

# Generate documentation
make docs

DevNet Testing

# Start local devnet
make devnet

# Run spamoor against devnet
make devnet-run

# Clean up devnet
make devnet-clean

Git Workflow

Branch Strategy

master: Main development branch
feature/*: New features and enhancements
fix/*: Bug fixes
docs/*: Documentation updates

Commit Standards

Use conventional commit format: type(scope): description
Types: feat, fix, docs, refactor, test, chore
Include issue references when applicable
Keep commits atomic and focused

Pull Request Process

Create feature branch from master
Implement changes with tests
Update documentation if needed
Ensure all tests pass
Submit PR with clear description
Address review feedback
Squash and merge when approved

Testing Strategy

Unit Testing

Test individual functions and methods
Mock external dependencies (RPC clients, databases)
Use table-driven tests for multiple scenarios
Aim for good coverage of business logic

Integration Testing

Test complete scenarios end-to-end
Use local devnet for blockchain interactions
Verify transaction generation and submission
Test daemon API endpoints

Read the full file on GitHub · 178 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.

yesterday First seen · 178 lines · 7 tokens per session scan A aaef510c2d84

Subscribe to this mod's changes

development_workflow is a cursor rule published in the GitHub repository ethpandaops/spamoor (79 stars, last pushed 3d ago), licensed MIT. It adds 7 tokens to every session and 967 once invoked, about $0.0000 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-30.

Backend and APIs Git and workflow Testing ethereum spamming-tool

development_workflow