weave-cli

A command-line entry point for setting up, auditing, and monitoring Weave Protocol security in an AI-agent project.

In plain words
What is it for?
Use it to initialize framework-specific security code, audit project dependencies before deployment, and launch a monitoring dashboard.
Why use it?
It reduces the manual work of choosing security setup, checking dependencies for supply-chain risk, and inspecting agent security activity.

Skill for Claude CodeCodex

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/tyox-all/weave_protocol/cli
Any agent
npx skills add Tyox-all/Weave_Protocol --skill cli
Clone the repo
git clone --depth 1 https://github.com/Tyox-all/Weave_Protocol

Made for: Claude Code, Codex.

Per session 136 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 963 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.00136 $0.00963
Opus 5 $0.00068 $0.00481
Sonnet 5 $0.00027 $0.00193
Haiku 4.5 $0.00014 $0.00096

Measured yesterday against content hash b83f45eb835e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

weave-cli 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 yesterday.

The scan reads SKILL.md. This mod also ships 13 executable files (src/cli.ts, src/commands/index.ts, src/commands/init.ts, …), 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.

cli/SKILL.md · 107 lines

How it starts

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

Weave Protocol CLI

The weave CLI is the front door to the Weave Protocol security suite. Use it to set up new projects, audit existing ones, and run the monitoring dashboard.

Commands

weave init

Sets up Weave Protocol in the current project. Detects framework, asks user to confirm choices, scaffolds security middleware.

Use when:

  • User starts a new AI agent project and asks for security
  • User mentions Weave Protocol but isn't sure which packages they need
  • User wants framework-specific security boilerplate (LangChain callback, MCP wrapper, SDK middleware)
npx @weave_protocol/cli init

weave audit

Delegates to Tollere to scan dependencies for supply chain risk.

Use when:

  • User asks "is my project safe?"
  • User is about to deploy and wants a final check
  • User wants to add CI gating for dependencies
npx @weave_protocol/cli audit

Exit codes: 0 = clean, 1 = warnings, 2 = critical.

weave dashboard

Launches the API server and opens the monitoring dashboard.

Use when:

  • User wants real-time visibility into Weave Protocol activity
  • User asks to "see what's happening" with their security
  • User is debugging an issue and wants the live feed
npx @weave_protocol/cli dashboard

weave doctor

Environment health check. Verifies Node version, package.json, .weaverc, installed packages, Claude Desktop MCP config.

Use when:

  • User says "something isn't working"
  • User just installed and wants to verify setup
  • Debugging a config issue

weave version

Prints CLI version + installed Weave Protocol package versions. Useful for bug reports.

Decision rules

Situation Suggested command
New project, "I want security" weave init
Existing project, no .weaverc weave init
Pre-deploy supply chain check weave audit
User wants live monitoring weave dashboard
Something broken weave doctor
User filed a bug weave version (include in report)

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

  1. yesterday First seen · 107 lines · 136 tokens per session scan A b83f45eb835e

Subscribe to this mod's changes

weave-cli is a skill published in the GitHub repository Tyox-all/Weave_Protocol (0 stars, last pushed 8d ago), licensed Apache-2.0. It adds 136 tokens to every session and 963 once invoked, about $0.0007 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.