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 commands/platinoff/poolai/git-pushgit 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.00000 | $0.02400 |
| Opus 5 | $0.00000 | $0.01200 |
| Sonnet 5 | $0.00000 | $0.00480 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
git-push 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 yesterday.
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Push (MSYS2 Bash, без .sh)
Add, commit, push — тільки команди в MSYS2 bash. Без скриптів .sh, без PowerShell, без cmd.
⚠️ Критично: тільки зовнішній MSYS2
Не запускай git із терміналу Cursor. З’являються:
CreateFileMapping/ Win32 error 5index.lock,Permission deniedу.git/objects- Обрізаний або некоректний вивід інтегрованого терміналу IDE
Рішення: відкривай MSYS2 UCRT64 з меню Пуск (окреме вікно) і виконуй команди там.
1. Відкрий MSYS2 bash
- MSYS2 UCRT64 з меню Пуск — обов’язково зовнішнє вікно (не термінал Cursor).
Закрий Source Control у Cursor перед git.
2. Перевірка (якщо команди не відпрацьовують)
Переконайся, що ти в bash і в каталозі репо:
which bash
pwd
Перейди в репо. Якщо диск S: — спробуй обидва варіанти:
cd /s/rust/poolAI
pwd
Якщо cd /s/rust/poolAI не працює:
cd "S:/rust/poolAI"
pwd
Має показати шлях до poolAI. Далі — блок з п.3.
3. Copy-paste блок (повторюваний цикл + Summary у коміті)
Виконуй по одній команді або копіюй блок цілом.
Правило Summary (агент / Composer)
| У staged є зміни в… | Summary у тілі коміта |
|---|---|
src/, tests/, crates/, Cargo.toml, Cargo.lock, [[bin]] / [[test]] |
Обов’язково (п.3a): що змінено, які cargo команди, FM/scope якщо є |
лише docs/, .cursor/, README, OpenAPI без коду |
Рекомендовано короткий Summary (1–2 буллети) |
нічого в src//tests//crates/ |
Subject достатньо, якщо лише docs/chore |
Перед комітом: git diff --cached --stat (або git status -sb) — якщо в diff є код → сформуй Summary з реального diff, не шаблон «заглушка».
Агент/Composer: subject + кілька рядків Summary в тілі коміта (див. п.3a); після push — самарі в чат (п.3b).
# rustup ПЕРШИЙ — інакше візьметься MSYS2 rustc 1.87 і cloud-sdk не збереться (потрібен rustc >= 1.88)
export PATH="$HOME/.cargo/bin:/c/msys64/ucrt64/bin:/c/msys64/usr/bin:$PATH"
export K8S_OPENAPI_ENABLED_VERSION=1.28
cd /s/rust/poolAI
/c/msys64/usr/bin/rm -f .git/index.lock
git status -sb
cargo fmt --all
# За потреби перед push (зміни в коді/тестах), як у CI:
# cargo test --lib --tests --features ml,enterprise,cloud
# cargo clippy --all-targets --all-features
# cargo test --test cloud_mock_integration --features cloud,cloud-sdk -- --test-threads=1
git add README.md Cargo.toml src/ tests/ scripts/ file_list.csv
git add .gitignore
git add -f docs/CHANGELOG.md docs/cloud/CLOUD_SDK_STATUS.md docs/concept/poolAI_concept_root.txt docs/README.md docs/INDEX_2026-03-17.md docs/catalog/FUNCTIONALITY_DIGEST_2026-04-06.md docs/ARCHITECTURE_BEST_PRACTICES.md docs/development/NEXT_STEPS_ARCHITECT_2026-03-17.md docs/development/HANDOFF_NEW_SESSION.md docs/development/README.md docs/development/NEXT_STEPS_2026-01-19.md docs/status/STABLE_STATE_SUMMARY.md docs/troubleshooting/GIT_PUSH_FAILED.md
git add -f .cursor/hooks.json .cursor/hooks/ .cursor/CHANGELOG.md .cursor/README.md .cursor/rules/ .cursor/commands/ .cursor/skills/
git add -f AGENTS.md opencode.json skills-lock.json .agents/ .opencode/skills/ .opencode/package.json
git status -sb
git commit -m "type(scope): subject" -m "Summary:" -m "- Зміни: (модулі/файли)" -m "- Перевірки: cargo fmt; (clippy/test — що саме)" -m "- Ризики/нотатки: не стаджити data/audit/*.log.gz; при os error 112 — cargo clean"
git push origin main
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.
- yesterday First seen · 167 lines · 0 tokens per session scan A 6119d07ac0a3
git-push is a command published in the GitHub repository platinoff/poolAI (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,400 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.