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/themulea/codex-agent-core-template/vault-lintnpx skills add TheMuleA/codex-agent-core-template --skill vault-lintgit clone --depth 1 https://github.com/TheMuleA/codex-agent-core-templateWrote 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/themulea/codex-agent-core-template/vault-lint)<a href="https://agentmods.dev/skills/themulea/codex-agent-core-template/vault-lint"><img src="https://agentmods.dev/badge/skills/themulea/codex-agent-core-template/vault-lint.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.01119 |
| Opus 5 | $0.00026 | $0.00560 |
| Sonnet 5 | $0.00010 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
vault-lint 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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vault-lint
Назначение
Проверяет здоровье локального vault и помогает поддерживать порядок.
Lint не исправляет автоматически. Он выявляет проблемы, разделяет их по уровню риска и предлагает точечные действия через обычный change workflow.
Область проверки
Перед проверкой определить область:
- Agent Core:
agent/,.agents/skills/, релевантные logs. - Active project:
projects/<project_id>/, project roadmaps, project pending items, project work plans и релевантные logs. - Raw/source layer:
raw/. - Output layer:
output/. - Structural compare scope: исходные и новые пути, если идёт структурное сравнение.
По умолчанию для project lint проверять только active project layer. Другие project layers не читать и не смешивать без отдельной причины или подтверждения пользователя.
Фактический project_id берётся из projects/index.md после выбора active project.
Что проверять
- Битые внутренние ссылки.
- Orphan pages.
- Неактуальные страницы.
- Слишком длинные content pages.
- Пустые placeholder-разделы.
- Planning items.
- Pending items.
- Необработанные источники в
raw/,raw/sources/или согласованном source inbox. - Дублирующиеся страницы.
- Страницы без источников, если источники должны быть.
- Data gaps — пробелы данных, которые мешают использовать страницу или раздел как рабочую базу знаний.
- Соответствие страниц
agent/protocols/page-conventions.md. - Соответствие источников
agent/protocols/provenance-policy.md. - Соответствие связей
agent/protocols/linking-policy.md. - Соответствие проверки
agent/protocols/lint-checklist.md.
Lint cadence
lint cadence — ритм, в котором ты предлагаешь проверку vault. Это не автоматическое расписание и не разрешение на запуск внешних инструментов.
Ты должен предлагать vault-lint:
- после серии ingest или крупного переноса данных из raw/source layer в Agent Core или project layer;
- после массового создания, переноса или обновления страниц;
- перед большим synthesis/query, когда вывод зависит от нескольких разделов и качества связей;
- перед переходом на новый этап работы, если накопились pending items, новые источники или изменения структуры;
- по прямому запросу пользователя: “проверь порядок”, “сделай lint”, “проверь базу”.
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.
- 4d ago First seen · 90 lines · 51 tokens per session scan A 1d5d0ee0fcaf
vault-lint is a skill published in the GitHub repository TheMuleA/codex-agent-core-template (11 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 1,119 once invoked, about $0.0003 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…