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/skills/filigree-workflow/SKILL.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/skills/foundryside-dev/plainweave/filigree-workflow)<a href="https://agentmods.dev/skills/foundryside-dev/plainweave/filigree-workflow"><img src="https://agentmods.dev/badge/skills/foundryside-dev/plainweave/filigree-workflow/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/foundryside-dev/plainweave/filigree-workflow"><img src="https://agentmods.dev/badge/skills/foundryside-dev/plainweave/filigree-workflow.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.00103 | $0.03335 |
| Opus 5.5 | $0.00041 | $0.01334 |
| Sonnet 5.5 | $0.00021 | $0.00667 |
| Haiku 4.5 | $0.00010 | $0.00333 |
Grade A, and why
filigree-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 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filigree Workflow
Filigree is an agent-native issue tracker that stores data locally in .filigree/.
This skill provides procedural knowledge for using filigree effectively — as a solo
agent or in a multi-agent swarm.
Core Workflow
Every task follows this lifecycle:
filigree ready → find available work (no blockers)
filigree show <issue-id> → read requirements and context
filigree transitions <issue-id> → check valid status transitions
filigree start-work <issue-id> --assignee <name> → atomically claim + transition into its working status
[do the work, commit code]
filigree close <issue-id> --reason="summary of what was done"
Or skip steps 1–3 entirely with filigree start-next-work --assignee <name> to grab the highest-priority startable issue.
Ready ≠ startable. The working status is type-specific (tasks →
in_progress, features →building). Bugs start attriage, which has no single-hop transition into work — they walktriage → confirmed → fixing. So a triage bug is ready but not directly startable:start-workon one returnsINVALID_TRANSITIONnaming the next status to move through, andstart-next-workskips it.readyitems carry astartableflag (and anext_actionhint when false). Pass--advanceto either command to walk the soft transitions automatically (triage → confirmed → fixing) instead of being blocked or skipped.
Always close with a --reason — it becomes audit trail for the next agent.
Priority Semantics
| Priority | Meaning | Action |
|---|---|---|
| P0 | Critical | Drop everything. Production is broken. |
| P1 | High | Do next. Current sprint must-have. |
| P2 | Medium | Default. Normal backlog work. |
| P3 | Low | Nice to have. Do when P1/P2 are clear. |
| P4 | Backlog | Someday. Don't schedule unless promoted. |
When triaging, use filigree batch-update <ids...> --priority=N for bulk changes.
What ships with it
3 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.
- 1mo ago First seen · 326 lines · 103 tokens per session scan A 88a794bcf600
filigree-workflow is a skill published in the GitHub repository foundryside-dev/plainweave (0 stars, last pushed 3mo ago), licensed MIT. It adds 103 tokens to every session and 3,335 once invoked, about $0.0004 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
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
omh-research-department
This is a Hermes-native research-department workflow skill.
omh-agent-board
This is a Hermes-native agent-board workflow skill.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.