vp-note-quality

vp-note-quality is a skill for Claude Code from voxpelli/vp-claude. It costs 49 tokens per session (1,721 once invoked), scanned A, original, MIT.

A checklist for writing notes about subjects without mentioning the knowledge graph or the research process. Basic Memory is a tool for storing and linking notes.

In plain words
What is it for?
Use it when creating or editing Basic Memory notes, especially to remove self-referential content.
Why use it?
It helps keep notes understandable when they are read outside the system where they were created.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the vp-knowledge plugin — 14 skills, 5 agents, 4 hooks shipped together

Good fit Use it when creating or editing Basic Memory notes, especially to remove self-referential content.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/voxpelli/vp-claude/vp-note-quality
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.

Any agent
npx skills add voxpelli/vp-claude --skill vp-note-quality
Clone the repo
git clone --depth 1 https://github.com/voxpelli/vp-claude

Made for: Claude Code.

Or install vp-knowledge, the plugin that ships this one along with the rest of its 14 skills, 5 agents, 4 hooks.

Wrote 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.

agentmods badge for vp-note-quality

README.md
[![agentmods](https://agentmods.dev/badge/skills/voxpelli/vp-claude/vp-note-quality/github.svg)](https://agentmods.dev/skills/voxpelli/vp-claude/vp-note-quality)
Your own site
<a href="https://agentmods.dev/skills/voxpelli/vp-claude/vp-note-quality"><img src="https://agentmods.dev/badge/skills/voxpelli/vp-claude/vp-note-quality/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.

agentmods 80×15 button for vp-note-quality

Your own site · 80×15
<a href="https://agentmods.dev/skills/voxpelli/vp-claude/vp-note-quality"><img src="https://agentmods.dev/badge/skills/voxpelli/vp-claude/vp-note-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,721 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00049 $0.01721
Opus 5 $0.00024 $0.00860
Sonnet 5 $0.00010 $0.00344
Haiku 4.5 $0.00005 $0.00172

Measured 10d ago against content hash 93e6492a84a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

vp-note-quality 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 10d 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/vp-note-quality/SKILL.md · 146 lines

How it starts

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

Note Quality Checklist

When writing or editing Basic Memory notes, apply these rules to prevent the "fourth-wall anti-pattern" — self-referential content that references the knowledge graph, the enrichment process, or the state of personal knowledge sources instead of focusing on the note's subject.

Root cause: Task-boundary collapse. When an agent evaluates whether a topic fits the graph AND writes the note, the evaluation leaks into the content. The fix is a firewall: discard graph-fitting analysis before writing.

Diagnostic question: "If this note were exported and read by someone who knew nothing about the enrichment session and had never heard of Basic Memory, would every sentence make sense?" If no — it is harmful self-reference.

Rules

  1. Subject test. Every sentence — including frontmatter prose fields like description — must be about the note's declared subject. Content about the knowledge graph, the enrichment session, or personal knowledge sources must be deleted before writing.

  2. No inventory claims. Never write "X has zero presence in Raindrop/Readwise/Basic Memory." Coverage state is ephemeral and becomes false immediately. It belongs in session notes, not permanent knowledge notes.

  3. No significance rankings. Never write "this is the most significant gap" or "this is the most important connection." These are editorial judgments about the session, not facts about the subject.

  4. Firewall graph-fitting analysis. If you assessed whether a topic fills a graph gap before writing, discard that analysis entirely. The note is not a report on the assessment; it is knowledge about the subject.

  5. [gap] means subject gap, not coverage gap. A [gap] observation records something unknown about the subject itself (e.g., "The mechanism by which X spread to Y is undocumented"). It never records that the subject was absent from Raindrop or Readwise.

  6. [raindrop] and [readwise] must cite artifacts. Only add these observations if you have a specific bookmark URL, title, or highlight text. "No Raindrop bookmarks exist" is not a valid observation. Prefer [quote], [source], [pattern], or [connection] for the insight itself — use [raindrop]/[readwise] only when the provenance IS the point.

Read the full file on GitHub · 146 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. 10d ago First seen · 146 lines · 49 tokens per session scan A 93e6492a84a8

Subscribe to this mod's changes

vp-note-quality is a skill published in the GitHub repository voxpelli/vp-claude (3 stars, last pushed 12d ago), licensed MIT. It adds 49 tokens to every session and 1,721 once invoked, about $0.0002 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

harden-memories

Audit the bd remember store and recommend which entries to prune, so each one earns its per-session bd prime injection cost. Read-only: it proposes a triage table plus the exact bd forget / migration commands; you run them. Use when bd remember entries have accumulated, feel stale, redundant, or conflicting, or when…

voxpelli/claude-beads · 185 tokens

synergy-tracker

Manage cross-project synergy tracking between sibling projects. Use when the user wants to log a shared pattern, a divergence, an extraction candidate, or something a sibling project has that this one doesn't. Also use when the user wants to promote synergy entries to Basic Memory (workflow 5). NOT for upstream…

voxpelli/claude-beads · 197 tokens

upstream-tracker

Manage upstream issue tracking for this project. Use when the user wants to log a bug or friction point in a vendor package or npm dependency, review open upstream items, resolve a tracked issue, run a trend review, generate the upstream observations section of a sprint retrospective, promote upstream observations to…

voxpelli/claude-beads · 186 tokens

retrospective

Run a sprint retrospective for this project. Use when the user says 'retrospective', 'retro', 'close out the sprint', 'what went well', 'generate retro', or wants to generate a RETRO-NN.md file. Reads UPSTREAM-.md files, recent git history, and conversation context to pre-populate the retrospective. Do NOT use for…

voxpelli/claude-beads · 91 tokens

swarm-wave

Orchestrate multi-agent development sprints with wave-based parallelism. Use when the user wants to plan a swarm sprint, partition work into file-disjoint waves, map file contention across open issues, run a post-wave quality gate with review agents, manage agent backpressure, run a parallel research wave, or…

voxpelli/claude-beads · 176 tokens

backlog-groomer

Manage the beads backlog for this project. Use when the user wants to review or triage open issues, reprioritize the backlog, identify obsolete issues to close, investigate a topic to inform future work, create new issues from research findings, or enrich an existing issue with external context. Trigger phrases…

voxpelli/claude-beads · 191 tokens