Borrowing it
Nothing to install: this file belongs to foundryside-dev/plainweave. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/foundryside-dev/plainweave/main/AGENTS.mdgit clone --depth 1 https://github.com/foundryside-dev/plainweaveWrote 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/instructions/foundryside-dev/plainweave/agents-md)<a href="https://agentmods.dev/instructions/foundryside-dev/plainweave/agents-md"><img src="https://agentmods.dev/badge/instructions/foundryside-dev/plainweave/agents-md/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/instructions/foundryside-dev/plainweave/agents-md"><img src="https://agentmods.dev/badge/instructions/foundryside-dev/plainweave/agents-md.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.02773 | $0.02773 |
| Opus 5.5 | $0.01109 | $0.01109 |
| Sonnet 5.5 | $0.00555 | $0.00555 |
| Haiku 4.5 | $0.00277 | $0.00277 |
Grade C, and why
plainweave AGENTS.md scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- filigree:instructions:v3.0.1:65e6fb25 --> Copies of this mod
1 near-identical copy found in the catalogue:
- plainweave CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filigree Issue Tracker
filigree tracks tasks for this project. Data lives in .filigree/. Prefer
the MCP tools (mcp__filigree__*) when available; fall back to the filigree
CLI otherwise.
Workflow
# At session start
filigree session-context # ready / in-progress / critical path
# Pick up the next startable issue (atomic claim + transition into its working status)
filigree start-next-work --assignee <name>
# ...or claim a specific issue
filigree start-work <id> --assignee <name>
# Do the work, commit, then
filigree close <id>
Use the atomic claim+transition verbs — work_start / work_start_next
(MCP) or start-work / start-next-work (CLI). Do not chain
work_claim (MCP) or filigree claim (CLI) with a subsequent status
update — the two-step form races against other agents; the combined verb is
atomic.
Ready ≠ startable. The working status is type-specific (tasks →
in_progress, features → building). Bugs start at triage, which has no
single-hop transition into work (triage → confirmed → fixing), so a triage
bug is ready but not directly startable: work_start on one returns
INVALID_TRANSITION naming the next status, and work_start_next skips it.
work_ready items carry a startable flag (plus a next_action hint when
false). Pass advance=true (MCP) / --advance (CLI) to walk the soft
transitions to the nearest working status automatically.
Observations: when (and when not) to use them
observation_create is a fire-and-forget scratchpad for incidental defects — things
you notice outside the scope of your current task (a code smell in a
neighbouring file, a stale TODO, a missing test for an edge case you happened
to spot). Notes expire after 14 days unless promoted. Include file_path and
line when relevant. At session end, skim observation_list and either
observation_dismiss or observation_promote for what has accumulated.
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 · 201 lines · 2,773 tokens per session scan C d0af15e1e5b2
plainweave AGENTS.md is an instructions file published in the GitHub repository foundryside-dev/plainweave (0 stars, last pushed 3mo ago), licensed MIT. It adds 2,773 tokens to every session, about $0.0111 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.