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 agentmods add skills/foundryside-dev/plainweave/legis-workflownpx skills add foundryside-dev/plainweave --skill legis-workflowgit clone --depth 1 https://github.com/foundryside-dev/plainweaveWhat 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.00120 | $0.04003 |
| Opus 5 | $0.00060 | $0.02001 |
| Sonnet 5 | $0.00024 | $0.00801 |
| Haiku 4.5 | $0.00012 | $0.00400 |
Grade A, and why
legis-workflow 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.
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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legis Workflow
Legis is the git/CI and governance side of the Weft suite. This skill is the
depth behind the lean CLAUDE.md block: the full CLI reference, the MCP tool
catalogue, the error/recovery table, and the worked patterns an agent actually
runs. Keep it faithful to the installed legis — when in doubt, legis --help
and legis <command> --help are authoritative.
What legis is
Legis answers what changed, in which branch/commit/PR/check context, and what governance or attestation state exists for that change? It is an SEI consumer (Loomweave remains the identity authority) and the suite's single governed judge — Wardline analyses trust; Legis governs it, one judge not two. It does not own issue state (Filigree) or code identity (Loomweave); it adds branch/commit/PR/check context and a graded enforcement layer on top.
Enforcement is a 2×2 of policy cells, each agent-set, each a distinct override flow:
| Judge OFF | Judge ON | |
|---|---|---|
| Simple | chill — agent self-reports a recordable override; human reviews async (ACCEPTED_SELF) |
coached — an LLM wall evaluates the override before it records; ACCEPTED_BY_JUDGE or BLOCKED (not self-clearable) |
| Complex | structured — block + escalate; a human operator must sign off before the gate clears (ESCALATED_PENDING) |
protected — full machinery: HMAC-signed verdicts, decay sweep, override-rate gate, operator override |
The operating invariant is agent-first: humans on the loop, not in the loop. Every cell produces an append-only audit trail keyed on SEI, so the record survives rename/move. The recorded override is the safety mechanism — an attributable audit event, never a silent pass.
Reaching the tools
Prefer the MCP tools (mcp__legis__*) when a Legis MCP server is attached; fall
back to the legis CLI otherwise. Each surface maps thinly over the same service
layer, so they agree on outcomes.
Identity is launch-bound. The MCP server is started with
legis mcp --agent-id <name>; that --agent-id is the actor for every override,
sign-off, and audit record the session produces. No tool schema accepts an actor
argument — you cannot spoof or override identity from a call. (Contrast the CLI's
sei-backfill --actor, which stamps appended backfill events from a one-shot
command, not an interactive session.)
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.
- yesterday First seen · 253 lines · 120 tokens per session scan A 7990eac31207
legis-workflow is a skill published in the GitHub repository foundryside-dev/plainweave (0 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 4,003 once invoked, about $0.0006 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.
Other skills, from other repositories
gpt-researcher
GPT Researcher is an autonomous deep research agent that conducts web and local research, producing detailed reports with citations. Use this skill when helping developers understand, extend, debug, or integrate with GPT Researcher - including adding features, understanding the architecture, working with the API…
gpt-researcher
Autonomous deep research from Codex via MCP.
memmachine-memory
Use when an agent or model needs durable project, user, or session context from MemMachine, needs to save information to MemMachine memory, has requests involving mem-cli, memmachine, or memmachineclient, has insufficient conversation context, or is tempted to search local files for prior context that should come from…
telegram
Telegram Bot skill for sending and editing Telegram messages via Bot API. Use when Bub needs to: (1) Send a message to a Telegram user/group/channel, (2) Reply to a specific Telegram message with replytomessageid, (3) Edit an existing Telegram message, or (4) Push proactive Telegram notifications. Prefer rich…
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, or (6) Perform any GitHub…
frontend-code-review
Use only when the user explicitly requests a review or audit of frontend code under web/ or packages/dify-ui/. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, or backend-only code.