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 test-gatesgit 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/test-gates)<a href="https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/test-gates"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/test-gates/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/test-gates"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/test-gates.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.00097 | $0.00530 |
| Opus 5.5 | $0.00039 | $0.00212 |
| Sonnet 5.5 | $0.00019 | $0.00106 |
| Haiku 4.5 | $0.00010 | $0.00053 |
Grade A, and why
test-gates 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 1mo 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
Test Gates
Назначение
Проверяй изменение машинно-верифицируемыми проверками. Не доверяй текстовому объяснению без выполненных команд.
Связанный контекст: LLM Rules.
Вход
- Целевой репозиторий/папка.
- Список изменённых файлов.
- Риск-класс изменения.
- Локальные команды из
TEST_PLAN.mdиREADME.md.
Workflow
- Собери команды проверок из:
TEST_PLAN.mdAGENT_WORKFLOW.mdREADME.md
- Сначала выполни code gate:
- lint
- type/static/security checks (если настроены)
- Выполни test gate:
- unit tests
- integration tests
- Выполни release/smoke gate:
- smoke-команды из проекта
- Обработай flaky:
- пометь нестабильные проверки
- не засчитывай flaky-pass как полноценный green без политики проекта
- Сформируй единый gate report.
Жёсткие правила
- Не объявляй
GREEN, если обязательная команда не запускалась. - Если команда недоступна в среде, отмечай как
INCOMPLETE, а неPASS. - Если проверка падает, добавляй краткий корень проблемы и ближайший корректирующий шаг.
Выход (gate report)
Code gate: PASS|FAIL|INCOMPLETETest gate: PASS|FAIL|INCOMPLETESmoke gate: PASS|FAIL|INCOMPLETEFlaky notes:если естьOverall status: GREEN|YELLOW|RED
Критерии статуса
GREEN: все обязательные gates = PASS.YELLOW: нет FAIL, но есть INCOMPLETE/остаточный риск.RED: есть FAIL в обязательных 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.
- 1mo ago First seen · 57 lines · 97 tokens per session scan A 2596dc63156d
test-gates is a skill published in the GitHub repository dzhokhov/markdown-agent-vault-ru (2 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 530 once invoked, about $0.0004 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-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.
local-qa
A quality-assurance procedure that adds or updates tests and a repair guide whenever a software component changes. Quality assurance means checking that software still works and can be fixed later.
tt
Quality gate immediately after building: prove that what was just built actually works, while the context is still hot. Six steps: scope what changed, run live on real data, break it on purpose, show a counter or log proving it ran, root-cause any failure and re-run, then a verdict with evidence. Only a green verdict…
local-fb-alpha
A comment-analysis workflow that extracts links and ideas from Anton’s Facebook posts, fetches each resource, and tests it against an existing solution.
red-first-review
Review someone else's pull request by measuring which of its own guards its own test suite actually catches, via a small mutation matrix. Use when reviewing a PR, checking whether a regression test is real, or asked 'is this change actually tested?', 'does this test do anything', 'mutation test this'.
agentic-engineering
Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.