agentmods.dev

lore-dev-verification

lore-dev-verification is a skill for Claude Code, Codex from jordanhindo/lore. It costs 66 tokens per session (381 once invoked), scanned A, original, MIT.

A verification workflow for the Lore project, which provides infrastructure for storing and retrieving memories. It defines checks for code, workflow skills, command interfaces, migrations, privacy, packaging, and related changes.

In plain words
What is it for?
Use it before declaring Lore work complete, especially for skill changes, storage changes, retrieval tools, privacy behavior, or packaging updates.
Why use it?
It helps prove that changes work without exposing private conversation records, credentials, or personal memory data.

Skill for Claude CodeCodex

not rated 13 +1 2mo ago A scan 66 tokens original MIT
View the source file jordanhindo/lore
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/jordanhindo/lore/lore-dev-verification
Any agent
npx skills add jordanhindo/lore --skill lore-dev-verification
Clone the repo
git clone --depth 1 https://github.com/jordanhindo/lore

Made for: Claude Code, Codex.

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 lore-dev-verification

README.md
[![agentmods](https://agentmods.dev/badge/skills/jordanhindo/lore/lore-dev-verification.svg)](https://agentmods.dev/skills/jordanhindo/lore/lore-dev-verification)
Your own site
<a href="https://agentmods.dev/skills/jordanhindo/lore/lore-dev-verification"><img src="https://agentmods.dev/badge/skills/jordanhindo/lore/lore-dev-verification.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 381 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.00066 $0.00381
Opus 5 $0.00033 $0.00191
Sonnet 5 $0.00013 $0.00076
Haiku 4.5 $0.00007 $0.00038

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

Security

Grade A, and why

lore-dev-verification 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/validate-workflow-skill.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/lore-dev-verification/SKILL.md · 40 lines

What it actually says

Lore Dev Verification

Use this before calling Lore work complete. Lore is memory infrastructure, so verification must prove behavior without leaking private transcripts.

Quick Start

  1. Classify the change with references/verification-matrix.md.
  2. Run the targeted checks for that row.
  3. For skill changes, run the bundle and test-report validators: 
    node skills/lore-dev-verification/scripts/validate-workflow-skill.mjs skills/<skill-name>
  4. Run npm run check before merge unless the issue explicitly narrows the gate.
  5. Record what ran in the issue or skill evals/test-report.md.

Rules

  • Current files, tests, and runtime artifacts beat old transcript memory.
  • CLI and MCP surfaces must preserve JSON-envelope parity when they expose the same operation.
  • Fixtures must be synthetic or scrubbed. Never commit real transcript excerpts, credentials, private project text, or personal memory.
  • Real-store smoke checks are local proof only. Summarize counts/outcomes, not private message contents.
  • A workflow skill is not done until evals/test-report.md contains concrete eval evidence, validator output, trigger checks when relevant, privacy notes, and remaining risks.

References

  • references/verification-matrix.md maps change type to required checks.
  • references/skill-review.md explains workflow-skill review and report gates.
  • examples/ contains example verification plans for common Lore changes.
Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago First seen · 40 lines · 66 tokens per session scan A 93c7ebfafaa6

Subscribe to this mod's changes

lore-dev-verification is a skill published in the GitHub repository jordanhindo/lore (13 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 381 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.

Testing
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens