What is lock-project-stack?

A project setup skill that reads a dependency manifest—such as package.json or pyproject.toml—and locks the project to its declared library versions for documentation searches.

Use it to detect supported project manifests, record the dependency versions, report documentation coverage, and request missing library documentation.

It prevents documentation searches from showing instructions for newer library versions that the project does not use.

lock-project-stack — Skill by n24q02m

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/n24q02m/claude-plugins/lock-project-stack

Any agent

npx skills add n24q02m/claude-plugins --skill lock-project-stack

Clone the repo

git clone --depth 1 https://github.com/n24q02m/claude-plugins

Made for: Claude Code, Codex.

Or install wet-mcp, the plugin that ships this one along with the rest of its 5 skills.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 569 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00048	$0.00569
Opus 5	$0.00024	$0.00284
Sonnet 5	$0.00010	$0.00114
Haiku 4.5	$0.00005	$0.00057

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

Security

Grade A, and why

lock-project-stack 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.

Origin

This is a copy

100% identical to lock-project-stack — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/wet-mcp/skills/lock-project-stack/SKILL.md · 55 lines

How it starts

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

lock-project-stack

Bind a project to its declared dependency versions so every search(action="docs_query") call from inside that project surfaces docs for the exact versions you pinned, instead of "latest". Mirrors the Cabinets workflow from spec section 4.3.

Steps

Resolve the project root:
- If the user gave an absolute path, use it.
- Otherwise infer the root from the current workspace context (e.g. git rev-parse --show-toplevel output).
- Confirm at least one supported manifest exists: pyproject.toml, package.json, go.mod, or Cargo.toml.
Lock the project:
- Call search(action="docs_lock_project", project_path=<abs_path>).
- The response includes total detected libraries + indexed count (how many already have docs in Tier 1 or Tier 2). Surface both numbers to the user so they know how much coverage they have today.
Trigger Tier 2 ingestion for missing libraries (optional):
- Iterate the locked_libraries list; for entries with indexed == false, call search(action="docs_query", library=<name>, project_path=<abs_path>, query="<library> overview") once. The first call kicks off background Tier 2 ingestion; subsequent calls return real chunks.
Verify lock reuse:
- Re-call search(action="docs_query", library=<name>, project_path=<abs_path>, query=...) WITHOUT specifying version. The response should include a non-null lock_pin field matching the version from the manifest, confirming Cabinets is honoring the pin.
Surface the pin to the user:
- Summarize "Locked N libraries against versions X.Y.Z (M already indexed, K queued for Tier 2 ingestion)."

Best practices

Re-run after every dependency bump so the lock stays in sync with what is actually installed.
For monorepos, lock each workspace project separately — wet-mcp keys on absolute path so apps/web and apps/api get distinct locks.
The lock is a hint, not a hard constraint — callers can always override the version by passing it explicitly to docs_query.

Read the full file on GitHub · 55 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.

2d ago First seen · 55 lines · 48 tokens per session scan A 9c3a552b0e7c

Subscribe to this mod's changes

lock-project-stack is a skill published in the GitHub repository n24q02m/claude-plugins (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 48 tokens to every session and 569 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to lock-project-stack, differing in 0 lines, and is treated as a copy.

anthropic claude claude-code hooks marketplace mcp

lock-project-stack

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

lock-project-stack

Steps

Best practices

What this file has done since we first saw it

Other skills, from other repositories

persona-triggers

persona-format

persona-accountant

persona-marketer

persona-safety

persona-lawyer