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/scripts-structuregit clone --depth 1 https://github.com/speraxos/SperaxOS-AI-AgentsWhat 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.01060 | $0.01060 |
| Opus 5 | $0.00530 | $0.00530 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
scripts-structure 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 3d 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 scripts-structure — 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scripts Directory Structure Guide
This project uses an optimized, modular scripts directory structure for better maintainability and clear separation of concerns.
📁 Directory Structure Overview
The scripts/ directory is organized into the following modules:
Core Module (scripts/core/)
- scripts/core/constants.ts - Central configuration and constants
- scripts/core/model.ts - OpenAI model configuration
Utility Modules (scripts/utils/)
- scripts/utils/file.ts - File operations (read, write, directory management)
- scripts/utils/common.ts - General utility functions (string processing, arrays)
Processing Modules
- scripts/parsers/agent-parser.ts - Parse Agent configuration files
- scripts/processors/category-processor.ts - AI-powered category assignment
- scripts/processors/i18n-processor.ts - Internationalization and translation
- scripts/validators/agent-validator.ts - Schema validation and formatting
Build System
- scripts/builders/agent-builder.ts - Build all language versions of Agent files
- scripts/formatters/agent-formatter.ts - Format and process Agent configurations
Command Line Tools (scripts/commands/)
- scripts/commands/build.ts - Main build command
- scripts/commands/format.ts - Format Agent files
- scripts/commands/test.ts - Validation tests
- scripts/commands/test-locale.ts - Multi-language validation
- scripts/commands/update-awesome.ts - Update README
- scripts/commands/auto-submit.ts - GitHub automation
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.
- 3d ago First seen · 98 lines · 1,060 tokens per session scan A 0f475dbea4e1
scripts-structure is a cursor rule published in the GitHub repository speraxos/SperaxOS-AI-Agents (7 stars, last pushed 8mo ago), licensed MIT. It adds 1,060 tokens to every session, about $0.0053 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to scripts-structure, 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.
i18n-translation-system
This project implements an intelligent translation system with incremental detection and language validation.
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.