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/functionality-management)<a href="https://agentmods.dev/rules/platinoff/poolai/functionality-management"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/functionality-management/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/functionality-management"><img src="https://agentmods.dev/badge/rules/platinoff/poolai/functionality-management.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.00000 | $0.01021 |
| Opus 5.5 | $0.00000 | $0.00408 |
| Sonnet 5.5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
functionality-management 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Менеджер функціоналу (PoolAI)
Коли користувач просить звірити функції, беклог, прогалини, тікети, наступні кроки або охопити документацію — спершу docs/catalog/FUNCTION_MANAGEMENT.md (таблиця FM-* і §5.1).
Короткий алгоритм
- Що вважається «зроблено» —
docs/status/STABLE_STATE_SUMMARY.md+ код (src/network/,src/services/,Cargo.tomlfeatures). - Індекс можливостей —
docs/catalog/FUNCTIONALITY_DIGEST_2026-04-06.md(крок 11). - Пріоритети — §5.1 у
docs/catalog/FUNCTION_MANAGEMENT.md; Architect —docs/development/NEXT_STEPS_ARCHITECT_2026-03-17.md; операційний зріз —docs/development/HANDOFF_NEW_SESSION.md. - Горизонт (немає в коді) —
docs/concept/*, Grid/Solana концепти вdocs/development/; Rust ratio —RUST_RATIO_STRATEGY_2026-06-13.md, FM §5.13. - Якщо в доках порожньо —
git log --oneline -n 30,docs/archive/,rg TODO|FIXMEуsrc/.
Охоплення docs (без повного читання всього репо)
Таксономія: docs/STRUCTURE.md. Обхід за шарами, не всіма .md підряд:
| Шар | Шляхи | Навіщо |
|---|---|---|
| Канон 1–12 | README.md, docs/INDEX_2026-03-17.md, docs/development/NEXT_STEPS_ARCHITECT_*, HANDOFF_*, docs/catalog/*, docs/ARCHITECTURE_*, docs/performance/*, .github/workflows/ci.yml, file_list.csv |
Єдиний порядок і пріоритети |
| Статус | docs/status/STABLE_STATE_SUMMARY.md, CURRENT_STATUS.md (якщо потрібен зріз %) |
Заявлений стабільний стан |
| Розробка | docs/development/AUTO_RUN_SESSION_*.md (найновіший), AUTO_DEV_PATTERNS.md, docs/development/README.md |
Авторозробка + патерни |
| Концепт | docs/concept/poolAI_concept_root.txt, GRID_*, SOLANA_*, JOB_LAYER_* |
Concept-only vs код |
| Спадщина | docs/archive/, плоскі docs/*.md |
Лише через rg/посилання з INDEX; не канон |
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 · 42 lines · 0 tokens per session scan A 101534ce2993
functionality-management is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,021 tokens. 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.