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 dzhokhov/markdown-agent-vault-ru --skill owner-only-dev-orchestratorgit clone --depth 1 https://github.com/dzhokhov/markdown-agent-vault-ruWrote 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/dzhokhov/markdown-agent-vault-ru/owner-only-dev-orchestrator)<a href="https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/owner-only-dev-orchestrator"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/owner-only-dev-orchestrator/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/dzhokhov/markdown-agent-vault-ru/owner-only-dev-orchestrator"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/owner-only-dev-orchestrator.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.00111 | $0.00681 |
| Opus 5 | $0.00056 | $0.00341 |
| Sonnet 5 | $0.00022 | $0.00136 |
| Haiku 4.5 | $0.00011 | $0.00068 |
Grade A, and why
owner-only-dev-orchestrator 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 10d 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.
What it actually says
Owner-Only Dev Orchestrator
Назначение
Выполняй end-to-end контур для задач разработки: контракт задачи -> реализация -> самопроверка -> решение для владельца.
Связанный контекст: LLM Rules.
Обязательные источники правил
Перед работой прочитай:
Workflow
- Определи целевой репозиторий/папку кода.
- Проверь наличие обязательных артефактов процесса в репозитории:
AGENT_WORKFLOW.mdTEST_PLAN.mdRELEASE_CHECKLIST.mdCHANGELOG.mdINCIDENT_RUNBOOK.md
- Если артефактов нет, создай их из
meta/templates/до рискованных изменений. - Зафиксируй task contract:
- Goal
- Scope
- Out of scope
- Risk class (
low|medium|high) - Required validations
- Выполни реализацию малыми, логическими шагами.
- Вызови
$test-gatesдля прогонки quality gates. - Если есть релизная часть, high-risk изменение или инцидент, вызови
$release-rollback. - Сформируй owner decision packet и верни только управленческое решение.
Ограничения автономии
- Не выполняй destructive/history-rewrite действия без явного подтверждения.
- Не меняй секреты/доступы/production-конфигурацию без подтверждения.
- Не объявляй
GREEN, если не пройдены обязательные проверки.
Формат ответа владельцу
Всегда заверши ответ блоком:
STATUS: GREEN | YELLOW | REDЧто изменилось:1-2 строки без техжаргонаЧто проверено:краткий список gate-результатовНужно от владельца:Release | Hold | Rollback
Критерии статуса
GREEN: все обязательные gates пройдены, rollback-путь подтверждён.YELLOW: часть проверок неполная или есть управляемые риски.RED: обязательные gates провалены или риск неприемлем; релиз запрещён.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 59 lines · 111 tokens per session scan A 2c76adac6023
owner-only-dev-orchestrator is a skill published in the GitHub repository dzhokhov/markdown-agent-vault-ru (2 stars, last pushed 3d ago), licensed MIT. It adds 111 tokens to every session and 681 once invoked, about $0.0006 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
pos-verify
Use this immediately after files are created, edited, moved, deleted, or materially rewritten inside PersonalOS. Verifies that new truth was routed to the correct owner, written in the correct file shape, and still follows POS conventions. Do NOT use for whole-vault deep audits; use system-health-check.
skillify
Use this when {{username}} asks to skillify a repeated workflow, determine whether it deserves a reusable PersonalOS skill, or harden an existing workflow into a tested resolver-reachable capability. Do NOT use for one-off notes, ordinary execution, or already-specified skill authoring; use write-skill.
write-skill
Use this when the user wants to create a new shared PersonalOS skill under skills/ or revise a specified PersonalOS skill and the scope is already clear. Do NOT use for raw workflow capture or deciding whether work should become a skill; use skillify first. Do NOT use for repo-local or agent-local skills unless…
priority-dashboard
Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.
lint-brain
Run health checks over the brain vault - find orphan notes, broken wikilinks, missing frontmatter, stale projects, and missing cross-links. Use when asked to "lint the brain", "health check", "vault hygiene", or "/lint-brain".
log
Use this when a PersonalOS work session, chat outcome, personal reflection, or provided source should be persisted into the modular Daily context and any already-owned canonical files. Do NOT use for single-call processing, single-source knowledge ingestion, Gmail/WhatsApp propagation, or Lexware booking.