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 skills/platinoff/poolai/poolai-documentationnpx skills add platinoff/poolAI --skill poolai-documentationgit clone --depth 1 https://github.com/platinoff/poolAIWhat 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.00060 | $0.01547 |
| Opus 5 | $0.00030 | $0.00773 |
| Sonnet 5 | $0.00012 | $0.00309 |
| Haiku 4.5 | $0.00006 | $0.00155 |
Grade A, and why
poolai-documentation 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PoolAI — документація та витяг функціоналу
Canon: .agents/skills/poolai-documentation/. Client copies under .cursor/skills/ and
.opencode/skills/ must stay identical (Cursor + OpenCode).
Runtime stack (перед будь-якою імплементацією)
- Читай
.cursor/rules/runtime-stack-policy.mdc— Rust primary; no Python runtime; target 90–95% Rust —RUST_RATIO_STRATEGY_2026-06-13.md. - API tests — Rust
tests/(poolai-testing-policy.mdc); Playwright — browser only. - ML/TurboQuant —
src/ml/(Rust). Архівні docs з Python — не план імплементації. - Secrets: never stage
.env,*.pem/*.key,certs/*.pem,data/audit/*—SECRETS_MANAGEMENT.md§1 ·certs/README.md.
Код репозиторію (не плутати папки)
docs/development/REPOSITORY_LAYOUT.md—src/vssrc/bin/vsbin/vsscripts/vstests/vscrates/.- Нові dev launchers →
bin/; toolchain →scripts/; Rust CLI →src/bin/.
Канонічний порядок (завжди той самий)
Узгодь посилання з кореневим README.md → кроки 1–12:
- Кореневий
README.md docs/INDEX_2026-03-17.md(для структури папок і спадщини —docs/STRUCTURE.md)docs/development/NEXT_STEPS_ARCHITECT_2026-03-17.md(таблиця P1–P7 і підрозділ «Операційний порядок» — дзеркало §5.1 уFUNCTION_MANAGEMENT.md)docs/development/HANDOFF_NEW_SESSION.md- Концепція (
docs/concept/poolAI_concept_root.txt, Grid/Memory/Job,GRID_PROTOCOL_CONCEPT_2026-04-06.md,SOLANA_ADAPTER_CONCEPT_2026-04-06.md) docs/ARCHITECTURE_REVIEW.md,docs/ARCHITECTURE_BEST_PRACTICES.mddocs/performance/BENCHMARKS.md,PROFILING.md(Criterion +poolai_health_load/--jsonдляGET /api/v1/health).github/workflows/ci.ymlfile_list.csv(оновлюй також після змін уdocs/catalog/,.agents/skills/,.cursor/skills/,.opencode/skills/).cursor/commands/git-push.mddocs/catalog/FUNCTIONALITY_DIGEST_2026-04-06.md— витяг функціоналуdocs/catalog/FUNCTION_MANAGEMENT.md— керування функціоналом, тікетиFM-*, §5.1 (наступні кроки); правило.cursor/rules/functionality-management.mdc
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 · 74 lines · 60 tokens per session scan A 22d49e84e6ab
poolai-documentation is a skill published in the GitHub repository platinoff/poolAI (4 stars, last pushed 10d ago), licensed MIT. It adds 60 tokens to every session and 1,547 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…