agentmods.dev

vouch-record

A command for proposing structured records about people, organisations, or projects in a shared knowledge base. Each proposal includes a validated record page and can link related entities.

In plain words
What is it for?
Use it to file a contact, organisation, or project, add details such as a role or owner, and connect it to related records.
Why use it?
It prevents duplicate records and keeps new information in a review queue instead of adding it directly. A person must approve proposals before they become visible to searches.

Skill for Claude CodeCodex

91 +1 10d ago A scan 21 tokens original MIT
View the source file vouchdev/vouch
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/vouchdev/vouch/vouch-record
Any agent
npx skills add vouchdev/vouch --skill vouch-record
Clone the repo
git clone --depth 1 https://github.com/vouchdev/vouch

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 313 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.00021 $0.00313
Opus 5 $0.00010 $0.00156
Sonnet 5 $0.00004 $0.00063
Haiku 4.5 $0.00002 $0.00031

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

Security

Grade A, and why

vouch-record 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.

adapters/openclaw/skills/vouch-record/SKILL.md · 29 lines

What it actually says

/vouch-record

File "$ARGUMENTS" as a typed record: an entity plus a kind-validated page, both as pending proposals. Requires the company-brain page kinds (vouch init --template company-brain; check with vouch schema list).

Steps:

  1. Decide the record shape: person -> entity type person + contact page (frontmatter: role, optional org, email); organisation -> company entity + org page; project -> project entity + project-record page (frontmatter: record_status, optional owner).
  2. Call kb_search first — if the entity already exists, propose only the page update (pass the existing page id as slug_hint) instead of a duplicate.
  3. Call kb_propose_entity, then kb_propose_page with page_type set to the record kind and the frontmatter in metadata. Cite a registered source when the record distills one (register the conversation via kb_register_source if the user is dictating facts).
  4. Link ownership or membership with kb_propose_relation where it's clear.
  5. Report every proposal id filed.

Never call kb_approve. One record per invocation; ask before batching.

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 · 29 lines · 21 tokens per session scan A 5e0b4a9988b9

Subscribe to this mod's changes

vouch-record is a skill published in the GitHub repository vouchdev/vouch (91 stars, last pushed 10d ago), licensed MIT. It adds 21 tokens to every session and 313 once invoked, about $0.0001 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.

Memory and contextaiai-brainassistantpersonalvibe-codingvouch
Related

Other skills, from other repositories

release-openclaw-maintainer

Prepare or verify OpenClaw stable, beta, and extended-stable releases, including backport discovery, changelogs, release notes, publish commands, and artifacts.

openclaw/openclaw · 41 tokens

openclaw-testing

Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.

openclaw/openclaw · 38 tokens

autoreview

Structured Codex, Claude, Amp, Pi, or Kimi code review when explicitly requested.

openclaw/openclaw · 22 tokens

release-openclaw-ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

openclaw/openclaw · 39 tokens

auto-qa

Continuously audit, live-test, and stress-test the current OpenClaw codebase across at least ten independently scoped subsystem lanes; default to 100 independently verified, landed root-cause fixes, maintain an evidence-backed report, and announce each merged pull request immediately. Use for OpenClaw-wide autonomous…

openclaw/openclaw · 90 tokens

openclaw-changelog-update

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

openclaw/openclaw · 30 tokens