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/virtual-development-team)<a href="https://agentmods.dev/rules/platinoff/poolai/virtual-development-team"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/virtual-development-team/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/virtual-development-team"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/virtual-development-team.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.01565 | $0.01565 |
| Opus 5.5 | $0.00626 | $0.00626 |
| Sonnet 5.5 | $0.00313 | $0.00313 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
virtual-development-team 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Віртуальна команда розробки (PoolAI VDT)
Ролі агентів — poolai-agent-roles.mdc. S0, MSYS2, commit — poolai-session-iteration.mdc. Стек — runtime-stack-policy.mdc.
Ітерація (один PH-S*)
flowchart LR
S0[S0 git+docs] --> Sprint[PH-S*]
Sprint --> Fmt[cargo fmt]
Fmt --> Test[cargo test-ci]
Test --> Docs[FM HANDOFF NEXT_SESSION]
Docs --> Push[git push + самарі]
| Крок | Дія |
|---|---|
| S0 | Спочатку df -h /s (+ check_target_disk.sh → cargo clean за потреби); потім git fetch; HANDOFF; FM §5.12 |
| Спринт | Один PH-S* з §5.12; scope лише файли спринту |
| Тести | cargo fmt --all → K8S_OPENAPI_ENABLED_VERSION=1.28 cargo test-ci; Raft — cargo test-raft-ci за scope |
| OpenAPI | Після API: cargo run --bin poolai-openapi-gap-audit (0) |
| E2E (UI) | Лише scope src/ui/ / axe / visual: export PATH="$HOME/.cargo/bin:/ucrt64/bin:/usr/bin:$PATH" → bash bin/e2e-playwright.sh --start |
| API wire | Rust tests/*_integration.rs — канон; Playwright API-smoke — legacy, не дублювати (poolai-testing-policy.mdc) |
| Доки | PH-S* → ✅ у FM §5.12 + HANDOFF + NEXT_SESSION_PROMPT |
| Git | MSYS2, git-push.md, git-commit-msys.mdc — push + самарі в кінці сесії |
Локальний CI vs GitHub
| Канон перед push | Ігнорувати для «готово» |
|---|---|
cargo test-ci |
gh run на GitHub |
cargo test-raft-ci (Raft scope) |
Linux-only visual baselines |
poolai-openapi-gap-audit (API scope) |
Pa11y у cloud без стенду |
bash bin/e2e-playwright.sh --start (лише UI / src/ui/ / axe / visual) |
on-demand baseline workflow |
| API-only спринт без UI | Playwright skip без stand — не блокує push якщо cargo test-ci green |
Research / project scan (PH-S* <10 відкритих)
Звичайна сесія (один PH-S):* п.1–3 нижче.
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 · 75 lines · 1,565 tokens per session scan A 04656af9451e
virtual-development-team is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed yesterday), licensed MIT. It adds 1,565 tokens to every session, about $0.0063 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
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.