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 expandingideas-ai/mcp-wet --skill lock-project-stackgit clone --depth 1 https://github.com/expandingideas-ai/mcp-wetWrote 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/expandingideas-ai/mcp-wet/lock-project-stack)<a href="https://agentmods.dev/skills/expandingideas-ai/mcp-wet/lock-project-stack"><img src="https://agentmods.dev/badge/skills/expandingideas-ai/mcp-wet/lock-project-stack.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.00048 | $0.00569 |
| Opus 5 | $0.00024 | $0.00284 |
| Sonnet 5 | $0.00010 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
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 7d 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.
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.
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-topleveloutput). - Confirm at least one supported manifest exists:
pyproject.toml,package.json,go.mod, orCargo.toml.
-
Lock the project:
- Call
search(action="docs_lock_project", project_path=<abs_path>). - The response includes
totaldetected libraries +indexedcount (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.
- Call
-
Trigger Tier 2 ingestion for missing libraries (optional):
- Iterate the
locked_librarieslist; for entries withindexed == false, callsearch(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.
- Iterate the
-
Verify lock reuse:
- Re-call
search(action="docs_query", library=<name>, project_path=<abs_path>, query=...)WITHOUT specifyingversion. The response should include a non-nulllock_pinfield matching the version from the manifest, confirming Cabinets is honoring the pin.
- Re-call
-
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/webandapps/apiget distinct locks. - The lock is a hint, not a hard constraint — callers can always
override the version by passing it explicitly to
docs_query.
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.
- 7d ago First seen · 55 lines · 48 tokens per session scan A 9c3a552b0e7c
lock-project-stack is a skill published in the GitHub repository expandingideas-ai/mcp-wet (0 stars, last pushed 2mo ago), licensed MIT. 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.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.