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 resumegit 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/resume)<a href="https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/resume"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/resume/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/resume"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/resume.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.00204 | $0.02792 |
| Opus 5 | $0.00102 | $0.01396 |
| Sonnet 5 | $0.00041 | $0.00558 |
| Haiku 4.5 | $0.00020 | $0.00279 |
Grade A, and why
resume 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Восстановление припаркованного контекста
Ты выполняешь протокол возврата — находишь все припаркованные задачи, показываешь пользователю, и после выбора загружаешь полный контекст проекта для продолжения работы.
Зачем это нужно
Каждая припаркованная задача — это незавершённый рабочий контекст, на создание которого были потрачены усилия. Без явного протокола восстановления эти точки теряются: пользователь забывает, что было припарковано, или тратит время на повторное погружение. Resume делает возврат дешёвым — агент сам подтягивает контекст и напоминает, на чём остановились.
Модель роутинга задач
Resume работает в рамках task-routing-модели (см. task-routing-methodology-2026-04.md и Правила 10–14 AGENTS.md). Это значит:
- Припаркованное состояние проекта может лежать в пяти разных местах, в порядке приоритета чтения:
<project>/plan.md §Blockers— первоклассные блокеры проекта (BLOCKED, DELEGATED-with-milestone-impact). Главный источник «что не даёт двигаться». Читается первым.<project>/tasks.md— шаги проекта с маркерами прерываний (NEED_INFO, STOPPED Active-step)<project>/log.md— записи PAUSED/RESUMED без активных блокеров (STOPPED)01_now/ops/<contour>/delegations/<person-slug>.md— открытые делегирования сотрудникам, из поляdue:можно вытащить статус01_now/personal/tasks.md— личные обязательства владельца (не через парковку, но могут всплыть по passive recall)
- При восстановлении контекста проекта порядок чтения служебных файлов: README → plan (включая §Blockers) → context → tasks → log (медленные слои опережают быстрые, как в write-protocol.md §5).
- Для каждого упомянутого в парковке сотрудника — passive recall по соответствующему
delegations/<slug>.md: что ещё висит на нём, нет ли related блокеров. - Маркера 💡 SPAWNED больше не ищем — новая идея не паркуется, она сразу маршрутизируется в свой целевой файл без прерывания (см. §5.4.4 методологии).
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 · 140 lines · 204 tokens per session scan A 698983f58b52
resume is a skill published in the GitHub repository dzhokhov/markdown-agent-vault-ru (2 stars, last pushed 3d ago), licensed MIT. It adds 204 tokens to every session and 2,792 once invoked, about $0.0010 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
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.
task-manager
Use this when {{username}} or an agent wants to add, review, prioritize, complete, defer, park, or inspect todos, open loops, confirmed actions, waiting states, or attention triggers. Maintains atomic records under operations/actions/ and operations/attention-triggers/ as the only local action truth. Do NOT use for…
wrap-session-up
End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
gws-obsidian-prep
Cross-skill recipe: fetch today's (or tomorrow's) Google Calendar events via gws CLI and create meeting prep notes in the Obsidian vault.
obsidian
Obsidian vault management — create notes, backlinks, tags, and Dataview queries via file operations.
weekly
Run the weekly review of the big-brain second brain: triage the inbox, walk active projects, reschedule or drop overdue tasks, check vault health, and write a review summary. Use when the user types /weekly, or asks for a "weekly review", "review my projects", "clean up my brain", "triage my inbox".