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/cryndoc/polisade-orchestrator/prnpx 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.svg" alt="Measured on agentmods" 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.02137 |
| Opus 5 | $0.00075 | $0.01069 |
| Sonnet 5 | $0.00030 | $0.00427 |
| Haiku 4.5 | $0.00015 | $0.00214 |
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 5d 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.
- ⛔ NEVER самодельный Python/curl в Bitbucket/GitHub REST API: `requests.post(".../pull-requests", json=...)`, чтение `BITBUCKET_DOMAIN1_TOKEN` / `BITBUCKET_DOMAIN2_TOKEN` через `subprocess` или `os.environ`, прямой `cur How it starts
The opening of the file, as written. The whole thing — 106 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
Имена параметров соответствуют argparse в scripts/polisade_vcs.py — единственный source of truth. Проверь: python3 {plugin_root}/scripts/polisade_vcs.py --help.
Алгоритм
-
Распарсить
$ARGUMENTSкак<subcommand> [args]. -
Смаппить короткую форму субкоманды на имя скрипта:
create → pr-create list → pr-list view → pr-view diff → pr-diff merge → pr-merge comment → pr-comment close → pr-close whoami → whoami (остаётся как есть) -
Определить
WORK_DIR = ${POLISADE_WORK_DIR:-.}— если вызов из worktree, скрипт должен читать локальный.state/PROJECT_STATE.jsonи.env. Caller (агент) обязан заранееcdв нужный каталог; статический fallback.намеренно не использует command substitution — корп-шелл (GigaCode CLI / codex sandbox) режет$()(см. anti-patterns ниже). -
Выполнить:
python3 {plugin_root}/scripts/polisade_vcs.py <script-cmd> <args> \
--project-root "${POLISADE_WORK_DIR:-.}"
- Человекочитаемо отформатировать результат:
create→ номер + URL + head branch.list→ таблица (number, head, state).view→ ключевые поля + URL.diff→ stdout как есть (уже text).merge/close/comment— краткая сводка (#N <state>,branch_deleted: yes/no, warnings если есть).whoami— инстанс и провайдер.
- На non-zero exit показать stderr + подсказку:
запусти /polisade:doctor для диагностики VCS.
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.
- 5d 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 10d ago), licensed Apache-2.0. It adds 150 tokens to every session and 2,137 once invoked, about $0.0007 per session on Opus 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
deep-execution
Executes agent-enhanced council queries as one Workflow of parallel Claude analyst agents that each query a provider, evaluate response quality, ask follow-up questions, and return a schema-enforced analysis with confidence ratings and blind spot analysis. Invoked when the --agents flag is used or when complex…
update-lid
Configure or reconcile a project for linked-intent development (LID). Dispatches on project state — fresh bootstrap, append directives to an existing agent-instructions file (AGENTS.md or CLAUDE.md), add missing mode marker, reconcile convention drift, or run mode transitions. Invoked as /update-lid. For fresh…
matryca-github
Apply Matryca maintainer standards for GitHub issues, pull requests, branches, reviews, merges, milestones, tags, releases, and remote comments. Use before any GitHub-facing action or artifact.
matryca-logseq-io
Choose safe direct-file versus Local HTTP API access for Logseq. Use when changing graph reads, writes, background indexing, live Logseq integration, authentication, or JSON-RPC communication.
sflo
Starts and manages SFLO factory runs through the configured runner. Use when the user explicitly asks to start, run, resume, list, kill, clean, or inspect an SFLO factory, including requests to build something with SFLO. Do not use when SFLO appears only in quoted text, documentation, examples, code, logs, or…
map-codebase
Bootstrap LID in an existing (brownfield) codebase. Deep-reads every file in the declared scope, offers lens-based clustering options, generates skeleton LLDs/HLD/EARS bottom-up, then creates arrow docs and prompts the user to flesh out the skeletons. Token-intensive by design. Use when asked to map a codebase…