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/syncnpx skills add cryndoc/polisade-orchestrator --skill syncgit 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/sync)<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/sync"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/sync.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 | $0.00011 | $0.02141 |
| Opus 5 | $0.00005 | $0.01071 |
| Sonnet 5 | $0.00002 | $0.00428 |
| Haiku 4.5 | $0.00001 | $0.00214 |
Grade A, and why
sync 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 4d 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.
- Самодельный Python/curl в Bitbucket/GitHub REST API утекает токены из How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/polisade:sync — Sync State from Artifact Files
Сканирует файлы артефактов, пересобирает derived-поля в PROJECT_STATE.json (readyToWork, inProgress, blocked, waitingForPM, inReview, artifactIndex).
Использование
/polisade:sync # Показать diff (dry-run по умолчанию)
/polisade:sync --apply # Показать diff и записать после подтверждения
Алгоритм
- Определить корень проекта.
- Запустить скрипт в режиме dry-run:
python3 {plugin_root}/scripts/polisade_sync.py {project_root}
- Распарсить JSON-ответ, показать diff пользователю.
- Если пользователь подтверждает — применить:
python3 {plugin_root}/scripts/polisade_sync.py {project_root} --apply --yes
Для неинтерактивного использования (CI, pipe):
python3 {plugin_root}/scripts/polisade_sync.py {project_root} --apply --yes
Формат вывода
polisade_sync.py всегда печатает один JSON-документ на stdout
(контракт OPS-108 — json.loads(stdout) обязан проходить). PM-friendly
сообщения и подтверждение интерактивного prompt'а уходят на stderr.
Полная таблица контрактов — docs/config-reference.md § Script JSON
output contracts.
Если всё синхронизировано
{
"status": "in_sync",
"artifacts_scanned": 12,
"touched_paths": [],
"stage_paths": []
}
Если обнаружен drift (dry-run)
{
"status": "drift_detected",
"artifacts_scanned": 12,
"changes": [
{"field": "readyToWork", "added": ["TASK-005"], "removed": ["TASK-003"]},
{"field": "inProgress", "added": ["TASK-003"]},
{"field": "artifactIndex", "added": ["TASK-005"], "changed": ["TASK-003"]}
],
"touched_paths": [".state/PROJECT_STATE.json", ".state/counters.json"],
"stage_paths": [".state/PROJECT_STATE.json", ".state/counters.json"],
"dry_run": true
}
После --apply --yes
{
"status": "applied",
"artifacts_scanned": 12,
"changes": [{"field": "readyToWork", "added": ["TASK-005"]}],
"touched_paths": [".state/PROJECT_STATE.json", ".state/counters.json"],
"stage_paths": [".state/PROJECT_STATE.json", ".state/counters.json"]
}
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.
- 4d ago First seen · 196 lines · 11 tokens per session scan A 4544ea303992
sync is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 9d ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,141 once invoked, about $0.0001 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
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…
Collaboration Management
Complete guide to multi-agent collaboration card management, including starting collaborations, joining teams, and creating custom collaboration cards.
collaboration-workflow
Complete guide to the OpenSquad multi-agent collaboration system with user authorization gates. Use this skill when starting a collaboration session, coordinating multiple agents, managing the collaboration board, or when you need to understand how to use boardupdate, boardlist, and other collaboration tools. Triggers…
product-discovery
File-first orchestrator for product discovery and spec frameworks. Frames the problem with a Discovery Lead, Product Analyst, or System Architect role. Spawns parallel framework agents (Double Diamond, How Might We, Jobs to Be Done, user stories with INVEST, EARS for AI-coder specs, Gherkin), synthesizes into a PRD or…
triage-for-autonomy
Use BEFORE starting an unattended run, to score an existing queue of open items — a to-do list, an issue tracker, plan steps, or a persistent open-items store — into what is safe to do now, what is autonomous but heavy, and what is gated on a human. Produces a tier verdict plus a gate reason per item, and ranks the…
update
Updates the vendored Sprint chain in bootstrapped repos from the plugin source. Refreshes scripts, subagents, MCP config, and git hooks. Use --all to update every registered repo. Leaves configuration and lifecycle files untouched.