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 ehlyzov/skills --skill candidategit clone --depth 1 https://github.com/ehlyzov/skillsWrote 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/ehlyzov/skills/candidate)<a href="https://agentmods.dev/skills/ehlyzov/skills/candidate"><img src="https://agentmods.dev/badge/skills/ehlyzov/skills/candidate/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/ehlyzov/skills/candidate"><img src="https://agentmods.dev/badge/skills/ehlyzov/skills/candidate.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.00045 | $0.00388 |
| Opus 5.5 | $0.00018 | $0.00155 |
| Sonnet 5.5 | $0.00009 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
normalize-note-deadline 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 15d 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
Нормализация сроков — НЕ ГОТОВ К ИСПОЛЬЗОВАНИЮ
Статус: BLOCKED. Этот файл — снимок незавершённого кандидата, не исполняемая окончательная политика.
Вход: JSON с text (строка) и reference_date (календарная дата YYYY-MM-DD). Успешный выход: JSON с deadline (YYYY-MM-DD либо null) и evidence (точная цитата из text). При отсутствии срока deadline=null.
Не дописывай правило «следующая пятница» без ответа владельца: ближайшая строго будущая пятница либо пятница следующей календарной недели. До согласования не выполняй зависимую нормализацию.
План обычного вызова после финализации: «Нормализуй срок: {"text":"Отправить отчёт в следующую пятницу","reference_date":"2026-10-16"}». План debug-вызова: тот же запрос с инструкцией debug=true и каталогом для диагностики вне каталога навыка. Это соглашение инструкции, а не универсальный флаг платформы. Результат задачи должен совпадать с обычным вызовом; вход, снимок навыка, фактический выход и краткие проверяемые объяснения сохраняются отдельно. При недоступной записи сообщи ограничение и не выдумывай пути.
TODO до готовности: согласовать правило дней недели, зафиксировать поведение невалидного входа и неприводимых формулировок, уточнить evidence при отсутствии срока, выполнить обычный и debug-прогоны.
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.
- 15d ago First seen · 19 lines · 0 tokens per session scan A e408a5fc88c0
normalize-note-deadline is a skill published in the GitHub repository ehlyzov/skills (2 stars, last pushed 16d ago), licensed MIT. It adds 45 tokens to every session and 388 once invoked, about $0.0002 per session on Opus 5.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-10-18.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…