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/plainweave-workflownpx skills add foundryside-dev/plainweave --skill plainweave-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.00152 | $0.02783 |
| Opus 5 | $0.00076 | $0.01392 |
| Sonnet 5 | $0.00030 | $0.00557 |
| Haiku 4.5 | $0.00015 | $0.00278 |
Grade A, and why
plainweave-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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plainweave Workflow
Plainweave is the Weft federation's requirements and verification authority —
"the permission-for-code-to-exist member." It maintains a code-up intent graph
(Loomweave SEI → requirement → goal) in a local .plainweave/ store and answers
one question for every public surface: "why does this exist?" It is advisory:
it surfaces facts and lets agents decide; it never emits an allow/block verdict.
Prefer the MCP tools (mcp__plainweave__*) when available; fall back to the
plainweave CLI. Every read CLI takes --json to emit a versioned envelope.
The model — three altitudes, one graph
goal strategic intent ("ship trustworthy federation seams")
↑ links
requirement a reviewable statement ("the producer must never silent-clean")
↑ binds
code (SEI) a Loomweave-identified public entity (function/class/module)
A node with no upward edge is an orphan — a reviewable question, not an error. Code that skips its bind is exactly what surfaces. Requirements are trivially mintable; consolidation ("these three are the same") is agent-driven off the corpus, never an automated verdict.
Core read workflow — the four intent primitives
plainweave intent coverage # north-star: fraction of public surfaces that answer "why?"
plainweave intent orphans code # unjustified nodes at an altitude: code | requirement | goal
plainweave intent trace code <node_id> # justification neighborhood up to goals / down to code
plainweave intent corpus # readable dump of requirements + their code/goal links
coverageis the self-computed north-star. It is honestly qualified in-band:denominator_complete,present_plugins, namespace scoping, bounded evidence. Scope the denominator with--exclude-namespace PREFIX(default excludesscripts.,tests.) and--surface-class {cli-command,entry-point,exported-api,http-route}. It never reports a silent clean when the denominator is partial.orphans <altitude>lists nodes with no upward justification edge. Triage, don't panic — an orphan is "should this be bound, or is it genuinely standalone?"trace <altitude> <node_id>walks both directions from a node.corpusis the artifact a curator reads to spot duplicates before consolidating.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 214 lines · 152 tokens per session scan A 675dde76ff23
plainweave-workflow is a skill published in the GitHub repository foundryside-dev/plainweave (0 stars, last pushed 1mo ago), licensed MIT. It adds 152 tokens to every session and 2,783 once invoked, about $0.0008 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
derive-nfr-from-driver
Derives measurable NFRs from a parent business driver.
derive-security-from-risk
Derives security requirements from a named threat.
plan
Structured technical planning before implementation — architecture and task breakdown.
requirements
Requirements-engineering expert that operates in three modes: (1) Elicitation — extract atomic, testable requirements from briefs, meeting notes, or system specs using EARS notation, with full attribute set (ID, type, priority, ASIL, verification method, source), flagging ambiguities as open questions; (2) Refinement…
aomi-transact
Build natural-language crypto/DeFi agents and EVM MCP plugins (Claude Code, Cursor, Codex, Gemini). Aomi turns prompts into wallet-signed txs on Ethereum, Base, Arbitrum, Optimism, Polygon, Linea — non-custodial, fork-simulated. 40+ apps: Uniswap, Aave, Lido, Morpho, GMX, Hyperliquid, Polymarket.
aomi-transact
Build natural-language crypto/DeFi agents and EVM MCP plugins (Claude Code, Cursor, Codex, Gemini). Aomi turns prompts into wallet-signed txs on Ethereum, Base, Arbitrum, Optimism, Polygon, Linea — non-custodial, fork-simulated. 40+ apps: Uniswap, Aave, Lido, Morpho, GMX, Hyperliquid, Polymarket.