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.
npx agentmods add rules/ethpandaops/spamoor/project_architecturegit clone --depth 1 https://github.com/ethpandaops/spamoorWhat 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.00005 | $0.00481 |
| Opus 5 | $0.00003 | $0.00241 |
| Sonnet 5 | $0.00001 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
project_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.
What it actually says
Spamoor Project Architecture
Spamoor is an Ethereum transaction spamming tool written in Go with a modular, scenario-based architecture.
Project Structure
Core Components
- cmd/: Entry points for the application
spamoor/: CLI tool for running individual scenariosspamoor-daemon/: Web-based daemon for managing multiple spammers
- daemon/: Daemon mode implementation with database management
- spamoor/: Core transaction handling logic (clients, wallets, pools)
- scenarios/: Pluggable transaction scenarios (each in its own directory)
- txbuilder/: Transaction construction utilities
- webui/: Web interface for daemon mode
- utils/: Shared utility functions
Key Architecture Patterns
Scenario-Based Design
- Each scenario is self-contained in
scenarios/<name>/ - Scenarios implement the
TxScenariointerface - Scenarios are registered in
scenarios/scenarios.go - Each scenario has its own README.md with documentation
Transaction Management
- Client pooling with RPC endpoint management
- Wallet management with hierarchical key derivation
- Transaction batching and submission coordination
- Configurable transaction pool management
Daemon Architecture
- SQLite database for persistent state
- REST API with Swagger documentation
- WebSocket support for real-time updates
- Metrics collection via Prometheus
Technology Stack
- Language: Go 1.25+
- Blockchain: Ethereum (using go-ethereum fork)
- Database: SQLite with GORM-like interface (glebarez/go-sqlite)
- Web Framework: Gorilla Mux + Negroni middleware
- Frontend: Bootstrap + vanilla JavaScript
- Documentation: Swagger/OpenAPI
- Metrics: Prometheus client
Build System
- Makefile: Primary build system
- Docker: Containerization support
- Go Modules: Dependency management
- Custom go-ethereum fork for EIP-7702 support
Key Design Principles
- Modular scenario architecture for extensibility
- Clean separation between CLI and daemon modes
- Comprehensive logging and metrics
- Docker-first deployment approach
- Configuration via YAML files and command-line flags
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.
- 2d ago First seen · 63 lines · 5 tokens per session scan A 677ba122289f
project_architecture is a cursor rule published in the GitHub repository ethpandaops/spamoor (79 stars, last pushed 4d ago), licensed MIT. It adds 5 tokens to every session and 481 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.
Other cursor rules, from other repositories
mermaid-diagram-preset
Mermaid sequence diagram preset for all Markdown docs in this repo. Gives rectangles and notes enough breathing room that they don't overlap the arrows around them.
50-wallet-schema
This site deals with Ethereum wallets. The processing pipeline is as follows.
20-typescript
Cursor rule "20-typescript" from walletbeat/walletbeat, covering global typescript rules, the typechecker is your friend, eslint is your friend, respect code structure and do not bypass.
documentation
Documentation discovery index for Lineth monorepo.
pkg-or-internal
BTC Package Placement Rules.
documentation-language
All documentation files (.md, .mdc) in this project must be written in English.