set-up-verified-documentation

A setup tool for adopting the validated-memory method in a project. It creates folders for curated knowledge and agent memory, plus configuration files that describe how the project uses them.

In plain words
What is it for?
Use it when starting validated-memory in a repository, optionally linking the harness's memory path, and checking that the adoption is configured correctly.
Why use it?
It gives a project a consistent place for trusted notes and persistent agent memory. It can also connect that memory to the location where the coding harness expects to find it.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/everywan-dev/claude-code-engineering/set-up-verified-documentation
Any agent
npx skills add everywan-dev/claude-code-engineering --skill set-up-verified-documentation
Clone the repo
git clone --depth 1 https://github.com/everywan-dev/claude-code-engineering

Made for: Claude Code, Codex.

Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 661 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00087 $0.00661
Opus 5 $0.00044 $0.00331
Sonnet 5 $0.00017 $0.00132
Haiku 4.5 $0.00009 $0.00066

Measured 2d ago against content hash 7328a1b86461, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

set-up-verified-documentation 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 2d 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.

skills/set-up-verified-documentation/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set up verified documentation

Adopting the plugin in a project is one command, run from the project root.

Bootstrap the layout

python3 -m validated_memory init

This scaffolds, creating each item only if missing (existing items are never touched):

  • knowledge/ -- empty; curated-knowledge units go here.
  • memory/ -- empty except for its index, memory/MEMORY.md.
  • validated-memory.md -- the adopter configuration: declares the extension, the id_prefix, and the probe registry (already mapping git_ref to the bundled probe).
  • knowledge-extension.md -- a valid, empty declared extension (fields: []).

init reports init: created <path> or init: kept <path> for each item, and is safe to re-run: it is idempotent and never overwrites a hand-edited file. See the README's init section for the full contract, including --harness-memory below.

Wire the harness's persistent memory (optional)

python3 -m validated_memory init --harness-memory PATH

Makes PATH a move-proof symlink to this project's memory/ directory, so the harness reads agent memory from wherever it expects it while the data stays versioned inside this repo. Safe to call repeatedly, including after the project is renamed or re-cloned -- it only ever re-points the symlink, never deletes data. The plugin's SessionStart hook (hooks/restore-memory-symlink.sh) already calls this automatically for an adopted project on every session start; running it by hand is only needed to wire a harness location the hook does not already know about.

Verify the adoption

Right after init, both enforcement commands must pass clean:

python3 -m validated_memory validate
python3 -m validated_memory lint

validate may still report a WARNING for an empty knowledge/ (no units to check) -- that does not gate. Any ERROR means the scaffold is broken; do not proceed until both commands are clean.

Next steps

  • Declare adopter-specific fields by editing knowledge-extension.md -- see the document-with-evidence skill and the README's "Declared extension" section.
  • Register a probe for each anchor kind your units will use, by adding an entry under probes: in validated-memory.md -- see the detect-stale-documentation skill and the README's probe section.
  • Start writing curated knowledge with the document-with-evidence skill.

Read the full file on GitHub · 68 lines

Changes

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.

  1. 2d ago First seen · 68 lines · 87 tokens per session scan A 7328a1b86461

Subscribe to this mod's changes

set-up-verified-documentation is a skill published in the GitHub repository everywan-dev/claude-code-engineering (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 87 tokens to every session and 661 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

skill-builder

Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.

yusufkaraaslan/Skill_Seekers · 38 tokens

sandbox-environment

Sandbox API reference, proven patterns, and library recommendations for evaluateexpression.

pssah4/vault-operator · 17 tokens

generate-ai-rules

Generate AI assistant configuration files for a repository — CLAUDE.md, AGENTS.md, and Cursor rules (.cursor/rules/.mdc) — from codebase analysis. Use whenever the user wants to create or update CLAUDE.md, AGENTS.md, agent rules, Cursor rules, AI coding assistant configuration, or "onboard AI tools" to a project, even…

divar-ir/ai-doc-gen · 91 tokens

learn-from-correction

Propose a principle edit to a skill or persona file based on a (agentoutput, humanoutput) correction pair. Outputs a proposal markdown for human review - never auto-edits the target file.

assafkip/kipi-system · 45 tokens

ai-rulez

Manage AI assistant governance rules across Claude, Cursor, Windsurf, Copilot, Gemini, and other tools using ai-rulez. Use when configuring rules, context, skills, domains, profiles, includes, plugins, or generating tool-specific outputs.

Goldziher/ai-rulez · 53 tokens

mstar-skill-authoring

Agent skill 撰写 / 重写 / 优化规范(SkillsBench 实验门控)。在新建任意 skill、大改 SKILL.md、改写 description 触发契约、压缩过长 body、评审 skill 结构、或判断某段行为塑形文案是否值得保留时读取。适用于任何领域的 skill,不限于本仓库专题;不用于普通应用实现。.

btspoony/mstar-harness · 96 tokens