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/tserentserenov/fmt-exocortex-template/day-opennpx skills add TserenTserenov/FMT-exocortex-template --skill day-opengit clone --depth 1 https://github.com/TserenTserenov/FMT-exocortex-templateWhat 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.00034 | $0.02157 |
| Opus 5 | $0.00017 | $0.01078 |
| Sonnet 5 | $0.00007 | $0.00431 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
day-open 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 today.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Day Open (протокол открытия дня)
Роль: R1 Стратег. Два выхода: DayPlan (git, 80+ строк) + compact dashboard (VS Code, 20-30 строк). Порядок: сначала DayPlan → потом compact. Дата: ПЕРВОЕ действие =
date. Режим:memory/day-rhythm-config.yaml→interactive: false= одним блоком, решения → «Требует внимания». Фильтр свежести: issues, видео, заметки — за 2 дня. Urgent — всегда. Issues — только actionable: пропускать read-only репо и upstream без push-доступа. Шаблоны:.claude/skills/day-open/templates.md(читать перед шагами 7a и 7d). Детали шагов:day-open/day-open-details.md
БЛОКИРУЮЩЕЕ: пошаговое исполнение
Day Open = протокол. Блокирующее требование — наблюдаемое свойство: ни один шаг не пропущен молча; каждый шаг отмечается ДО перехода к следующему. Инструмент по умолчанию — список задач сессии (TodoWrite): каждый шаг → отдельная задача (pending → in_progress → completed). TodoWrite недоступен в сессии (клиент не выдал инструмент — штатная ситуация, зависит от сборки клиента) → НЕ останавливаться и НЕ вести протокол «в уме»: сообщить пилоту одной строкой («пошаговый контроль без TodoWrite — веду явную нумерацию»), вести шаги явной нумерацией в ответах («Шаг X из Y: <название> — выполнен») с отметкой каждого перед переходом к следующему, факт замены зафиксировать в отчёте открытия дня. Шаг невозможен → blocked (не пропускать молча). Почему: без явного трекинга агент пропускает шаги из-за загрязнения контекста (SOTA.002). Правило сформулировано через свойство, а не через конкретный инструмент: доступность инструментов контролирует клиент, не шаблон (issues #561, #563).
Алгоритм
0. Extensions (before)
bash .claude/scripts/load-extensions.sh day-open before → Exit 0: Read каждый файл, выполнить. Exit 1: пропустить.
1. Вчера
Прочитать вчерашний DayPlan (только секции «Итоги», «Завтра начать с», «Требует внимания»). Коммиты за вчера по всем $IWE_WORKSPACE/*/ репо.
What ships with it
2 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.
- today Changed · +1 lines c23d798b21ff
- yesterday First seen · 112 lines · 34 tokens per session scan A c5309ba2ae2c
day-open is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (48 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 2,157 once invoked, about $0.0002 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-30.
Other skills, from other repositories
data-profiling
Use BEFORE dispatching any subagent that needs to understand the dataset. Generates a high-density, PII-free data profile in Markdown so subagents receive structured context instead of raw data.
leakage-guard
Use whenever building features for time-series or any temporal dataset. Enforces strict temporal integrity: no future data in features, no post-event information, correct CV strategy.
verification-before-delivery
Use when any analysis, model, or report is claimed to be complete. Runs mandatory artifact integrity, statistical evidence, and reproducibility checks before any delivery.
analysis-manifest
Use at the START of every analysis session and at the END of every skill stage. Maintains artifacts/analysismanifest.json as the single source of truth for analysis state, preventing context drift across long sessions.
data-exploration
Use when exploring any dataset for the first time, or when asked to perform EDA. Enforces systematic exploration before any modeling or transformation.
executing-plans
Use when executing a written analysis plan task by task. Manages task state, enforces two-stage review (statistical first, then code quality), and gates manifest updates behind completed reviews.