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.
git clone --depth 1 https://github.com/platinoff/poolAIWrote 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/platinoff/poolai/project-structure)<a href="https://agentmods.dev/rules/platinoff/poolai/project-structure"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/project-structure/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/platinoff/poolai/project-structure"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/project-structure.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01214 | $0.01214 |
| Opus 5.5 | $0.00486 | $0.00486 |
| Sonnet 5.5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
project-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Structure Rules
Runtime stack (канон)
- Primary: Rust —
src/,tests/,crates/(див..cursor/rules/runtime-stack-policy.mdc, alwaysApply). - UI: JavaScript у
src/ui/; E2E —e2e/(TypeScript). - Python: заборонено в репозиторії (0×
.py); OpenAPI audit —cargo run --bin poolai-openapi-gap-audit. - Java: у репо немає; не додавати без явного запиту.
- Архівні docs з Python — ігнорувати для імплементації.
Repository layout (люди vs Cargo)
Повний опис: docs/development/REPOSITORY_LAYOUT.md.
| Шлях | Призначення |
|---|---|
src/ |
Rust product code (library + main) |
src/bin/ |
Cargo binaries only — cargo run --bin NAME |
bin/ |
Dev/ops launchers — .sh / .ps1 (run, LAN, verify, e2e) |
scripts/ |
Toolchain / deploy — MSYS PATH, gcc, build verify, git helpers |
tests/ |
Integration tests (Rust convention) |
crates/*/src/ |
Workspace members (e.g. poolai-solana-adapter) |
Не плутати: кореневий bin/ ≠ src/bin/. Rust .rs binaries тільки в src/bin/.
Directory Organization
src/- Source code (all Rust modules)tests/- Integration tests (all test files)docs/- Documentation (all markdown files)docs/troubleshooting/- Troubleshooting guides (QUICK_FIX_MSYS2.md, etc.)
bin/- Dev/ops shell scripts (launch, LAN stand, verify, cargo helpers)scripts/- Toolchain, MSYS setup, deployment helpersdocker/- Docker files (Dockerfile, docker-compose.yml).agents/skills/- Canon Agent Skills (Cursor + OpenCode): marketplace copies +abracadabra,poolai-documentation.cursor/- Cursor agent configuration (rules, commands, plans, native skill mirrors).cursor/rules/- All Cursor rules (including.cursorrulesmoved here).cursor/skills/- Cursor-native mirrors of project skills (keep identical to.agents/skills/)
.opencode/skills/- OpenCode-native mirrors of project skills (keep identical to.agents/skills/)AGENTS.md- OpenCode always-on canon (same VDT as alwaysApply Cursor rules)
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.
- 1mo ago First seen · 97 lines · 1,214 tokens per session scan A d04356db6a6b
project-structure is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed yesterday), licensed MIT. It adds 1,214 tokens to every session, about $0.0049 per session on Opus 5.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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.