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 voxpelli/vp-claude --skill knowledge-primegit clone --depth 1 https://github.com/voxpelli/vp-claudeWrote 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/voxpelli/vp-claude/knowledge-prime)<a href="https://agentmods.dev/skills/voxpelli/vp-claude/knowledge-prime"><img src="https://agentmods.dev/badge/skills/voxpelli/vp-claude/knowledge-prime.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.1 | $0.00128 | $0.02374 |
| Opus 5 | $0.00064 | $0.01187 |
| Sonnet 5 | $0.00026 | $0.00475 |
| Haiku 4.5 | $0.00013 | $0.00237 |
Grade A, and why
knowledge-prime 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 8d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Primer
Surface project-relevant Basic Memory knowledge as a concise context brief. Identifies which dependencies and tools are documented, loads key gotchas and patterns, and highlights gaps worth filling.
Flags
--deep— expand observation loading from 800 to 2000 tokens and include[pattern],[feature],[usage]categories alongside the default critical categories. Also expands graph traversal from top 6 to top 12 notes.
Edge Cases
- No manifest files found — report "No package or tool manifest files detected in the current directory" and skip steps 2–5. Suggest running in a project root.
- Empty BM directories — treat as 0 documented. Don't error.
- Very large dependency lists (100+) — cap at top 50 by frequency/ alphabetical for the cross-reference. Note total count in the brief.
--deepon a small graph (<10 notes) — treat as compact mode. Report "Graph has fewer than 10 notes — showing all relevant notes."
Workflow
1. Identify project stack
Detect manifest files in the current working directory:
| Manifest file | Ecosystem | BM directory | Prefix |
|---|---|---|---|
package.json |
npm | npm/ |
npm: |
Cargo.toml |
Rust | crates/ |
crate: |
go.mod |
Go | go/ |
go: |
composer.json |
PHP | composer/ |
composer: |
pyproject.toml or requirements.txt |
Python | pypi/ |
pypi: |
Gemfile |
Ruby | gems/ |
gem: |
Brewfile |
Homebrew | brew/, casks/ |
brew:, cask: |
.github/workflows/*.yml |
Actions | actions/ |
action: |
Dockerfile |
Docker | docker/ |
docker: |
.vscode/extensions.json |
VSCode | vscode/ |
vscode: |
Use Read to check for root-level manifest files — do not use Glob, which recurses into node_modules/ and similar directories. Use Glob only for wildcard paths like .github/workflows/*.yml. For detected package manifests, use
Read to extract dependency names:
package.json→dependencies+devDependencieskeysCargo.toml→[dependencies]+[dev-dependencies]tablesgo.mod→requireblockcomposer.json→require+require-devkeyspyproject.toml→[project.dependencies]ordependencieskeyrequirements.txt→ package names (before==/>=/etc.)Gemfile→gem '...'lines
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.
- 8d ago First seen · 225 lines · 128 tokens per session scan A 463e68693984
knowledge-prime is a skill published in the GitHub repository voxpelli/vp-claude (3 stars, last pushed 10d ago), licensed MIT. It adds 128 tokens to every session and 2,374 once invoked, about $0.0006 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.
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…
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…
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…
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…
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…
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…