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/speraxos/speraxos-ai-agents/development-workflowgit clone --depth 1 https://github.com/speraxos/SperaxOS-AI-AgentsWrote 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/speraxos/speraxos-ai-agents/development-workflow)<a href="https://agentmods.dev/rules/speraxos/speraxos-ai-agents/development-workflow"><img src="https://agentmods.dev/badge/rules/speraxos/speraxos-ai-agents/development-workflow.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00774 |
| Opus 5 | $0.00000 | $0.00387 |
| Sonnet 5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00077 |
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 4d 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.
This is a copy
100% identical to development-workflow — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 115 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:
- Calls scripts/commands/format.ts
- Executes
formatAgents()function - Processes each agent through scripts/formatters/agent-formatter.ts
- Performs incremental translation detection
- Validates language accuracy
- Saves formatted and translated files
🚀 Development Best Practices
Before Making Changes
- Run
pnpm run type-checkto ensure TypeScript correctness - Test changes with a small subset of agents first
- 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
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.
- 4d ago First seen · 115 lines · 0 tokens per session scan A 4a6684683f6d
development-workflow is a cursor rule published in the GitHub repository speraxos/SperaxOS-AI-Agents (7 stars, last pushed 8mo 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. It is 100% identical to development-workflow, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
hyperliquid-net
Conventions for using HyperLiquid.Net when working with the HyperLiquid DEX in C#/.NET, including spot, futures, account, HIP-3 DEX, and HIP-4 outcome APIs. Apply when generating code that interacts with the HyperLiquid API.
whitebit-net
Conventions for using WhiteBit.Net when working with the WhiteBit cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with WhiteBit APIs.
xt-net
Conventions for using the XT.Net library when working with the XT cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the XT API.
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.
cli-error-handling
CLI command error handling patterns.