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 Weavatrix/weavatrix-js --skill skillgit clone --depth 1 https://github.com/Weavatrix/weavatrix-jsWrote 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/weavatrix/weavatrix-js/skill)<a href="https://agentmods.dev/skills/weavatrix/weavatrix-js/skill"><img src="https://agentmods.dev/badge/skills/weavatrix/weavatrix-js/skill/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.
<a href="https://agentmods.dev/skills/weavatrix/weavatrix-js/skill"><img src="https://agentmods.dev/badge/skills/weavatrix/weavatrix-js/skill.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.06277 |
| Opus 5.5 | $0.00024 | $0.02511 |
| Sonnet 5.5 | $0.00012 | $0.01255 |
| Haiku 4.5 | $0.00006 | $0.00628 |
Grade A, and why
weavatrix-js 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 1mo 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
weavatrix MCP
Structure-analysis tools over a prebuilt code graph plus the weavatrix analysis engines. The default
offline profile contains no HTTP tool and permits repository switching only through an
explicit local open_repo call. Use pinned when a shared MCP process must never change or inspect
outside its startup repository.
Step 0 — if the tools are missing
Tools are named mcp__weavatrix__…. If none are available, ask the user to register the server
(claude mcp add -s user weavatrix-js -- npx -y weavatrix-js <repoRoot>; Codex:
codex mcp add weavatrix-js -- npx -y weavatrix-js <repoRoot>), then retry.
First compare the selected profile with the graph_stats runtime line. Expected catalogs are 31
tools for pinned and 34 for offline. Weavatrix refuses
initialize, tools/list, and tool calls when the running package version differs from the
package.json version on disk, with a loud STALE_RUNTIME error; restart/reconnect rather than using
an old daemon. WEAVATRIX_ALLOW_STALE_RUNTIME=1 is only for deliberate source development. A custom
capability list needs crossrepo for trace_api_contract. Legacy network profile names fail loudly
and direct the user to the separate weavatrix-online package.
Profiles use the same npm package and binary:
offline(default): all local analysis and explicitopen_repo; no HTTP tools.pinned: local analysis with noopen_repo, no global/cross-repository graph access, and no HTTP tools.
Intent router
Weavatrix is not one report or three fixed workflows. Its 34 methods expose different bounded views and analyses over the same reusable graph. Start from the task and choose the smallest sufficient projection; expand only when the answer requires it.
Graph views and application understanding
- Confirm repository, graph freshness and build mode:
graph_stats; userebuild_graphonly for a reported fallback/error or an intentional mode/precision change. - Switch or inventory local repositories:
list_known_repos->open_repo->graph_stats. - See production module topology:
module_map; use this first for a large unfamiliar application. - See discovered communities and their members:
list_communities->get_community. - Find high-coupling hubs:
god_nodes; repeated call sites do not inflate unique connectivity. - Inspect one graph entity:
get_node; pass an exact node ID when labels are ambiguous. - Inspect direct one-hop relations:
get_neighbors; do not confuse it with transitive impact. - Find a connectivity path between two concepts:
shortest_path. It traverses the graph as undirected reachability, so it is not proof of call/dependency direction; confirm direction withget_neighborsandread_source. - Explore an unknown entry point or architectural question:
query_graph; pinseed_filesor exactseed_symbolswhen known. Userelation_filterplusflow_directionfor a bounded event, worker, queue, cron, CLI, or data-flow view; keep a broad natural-language result as orientation evidence. - Inspect one exact symbol deeply:
context_bundlefor the bounded edit workset;inspect_symbolfor the raw point query and on-demand JS/TS reference evidence. - Confirm graph evidence in source:
read_source; usesearch_codeonly for a narrow regex/glob check. Search is supporting evidence, not the repository-intelligence layer.
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.
- 1mo ago First seen · 375 lines · 60 tokens per session scan A 92f5811d0d1e
weavatrix-js is a skill published in the GitHub repository Weavatrix/weavatrix-js (0 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 6,277 once invoked, about $0.0002 per session on Opus 5.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
establishing-code-ownership
Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via distributed owners.yaml, products//product.yaml, and .github/CODEOWNERS). Use when assigning a reviewer, attributing a bug or slow query to a team, routing work, scoping a team-wide audit, or answering "who owns…
extending-hobby-smoke-tests
Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml. Use when adding an ingestion round trip, deciding whether a product belongs in Hobby CI, changing the CI Hobby service topology or API-key scopes, or diagnosing a smoke test that captures data…
react-doctor
Diagnose and fix React codebase health issues. Use when reviewing React code, fixing performance problems, auditing security, or improving code quality.
weavatrix-refactor-js
Apply hash-verified refactoring edit plans: a weavatrix-refactor-js plan producer computes and proves a plan against the read-only core, then applyeditplan previews it (issuing a confirm token), applies with automatic rollback, and verifiedchange proves it. The only Weavatrix component that writes code.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.