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 skills add cryndoc/polisade-orchestrator --skill prgit clone --depth 1 https://github.com/cryndoc/polisade-orchestratorWrote 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/skills/cryndoc/polisade-orchestrator/pr)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/pr"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/pr/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/skills/cryndoc/polisade-orchestrator/pr"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/pr.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.00150 | $0.04156 |
| Opus 5.5 | $0.00060 | $0.01662 |
| Sonnet 5.5 | $0.00030 | $0.00831 |
| Haiku 4.5 | $0.00015 | $0.00416 |
Grade A, and why
pr scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> Bare `git push` запрещён (push обязан проверяться сравнением remote SHA — OPS-028); самодельные REST/curl-вызовы к Bitbucket/GitHub запрещены; helper не транскрибируется в `/tmp`. How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:pr — Provider-Agnostic PR Operations
Обёртка над scripts/polisade_vcs.py для ручных операций с PR: просмотр списка, диффа, комментарии, merge, close. Провайдер определяется из .state/PROJECT_STATE.json → settings.vcsProvider (github по умолчанию, bitbucket-server при корпоративном self-hosted Bitbucket).
Перед первым вызовом для Bitbucket заполни .env (BITBUCKET_DOMAIN1/2_URL + TOKEN) — подсказка в env.example, валидация через /polisade:doctor.
Использование
/polisade:pr create --title T (--body B | --body-file F | --body-stdin) [--head BR] [--base main]
/polisade:pr list [--head BRANCH] [--state OPEN|MERGED|ALL]
/polisade:pr view <id>
/polisade:pr diff <id>
/polisade:pr merge <id> [--squash] [--delete-branch]
/polisade:pr comment <id> (--body T | --body-file F | --body-stdin)
/polisade:pr close <id>
/polisade:pr whoami
⛔ Если вызов скрипта на этом шаге ты СДЕЛАЛ, и он отклонён или не запустился (
Command references protected path/Install directory is read-protected/Filesystem Guard/the tool's default permission is 'deny', отказ песочницы, ненулевой exit без вывода) — STOP. Вызова не было — отказа нет: сначала выполни команду; этот блок описывает её вывод и сам ответом не служит. Процитируй отказ дословно. НЕ пересказывай по исходнику, что скрипт «сделал бы»; НЕ собирай dry-run вручную; НЕ переходи к apply/push/pr-create. НЕ транскрибируй скрипт (прочитать → записать копию в/tmpили в проект → запустить копию): копия не байт-идентична — уезжают классы символов в regex, форма возврата функций, пропадают целые функции — и молча меняется набор применённых изменений. Отказ инструмента — это отказ, а не результат. Доложи PM дословный текст отказа и назови следствие: без рабочего вызова скрипта этот шаг выполнить нечем. Причину не придумывай — её называет только сам текст отказа.
Имена параметров соответствуют argparse в scripts/polisade_vcs.py — единственный source of truth. Проверь: ${POLISADE_PYTHON:-python3} {plugin_root}/scripts/polisade_vcs.py --help.
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 Changed 2e0ac06b603f
- 8d ago Changed 014c77b1840b
- 9d ago Changed 633cb5d0396f
- 11d ago Changed 2e172bd6e264
- 12d ago Changed e328f7c60996
- 1mo ago Changed · +38 lines 89bbee37d0d6
- 1mo ago First seen · 106 lines · 150 tokens per session scan A 448a4ced9c54
pr is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 4d ago), licensed Apache-2.0. It adds 150 tokens to every session and 4,156 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
lanius
Skill "lanius" from markmhendrickson/ateles, covering lanius — github workflow coordinator, identity, principals, core job and workflow phases (feature issues).
orchestrate-issues
Drive a whole graph of GitHub issues to completion using background subagents. Queries the unblocked frontier through native GitHub issue dependencies, dispatches one implementer per ready issue into an isolated worktree, runs a spec-review agent against the result, lands the PR, then re-queries as each merge opens…
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.
meta-github-pr-watch-digest
Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.
triage-issues
Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content.
post-issue-comment
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments.