136 verified recipes
Verified AI workflows
that actually ship.
A screenshot shows what worked once. FlowStacks shows what still works: CI re-runs every recipe on each change, so the badge goes red the moment one breaks. Browse by tool, by use case, or by what it replaces.
$ npm run verify ✓ obsidian-claude-weekly-review 5/5 ✓ tldraw-make-real-sketch-to-code 5/5 ✓ obsidian-agent-harness 7/7 ✓ dedupe-and-rank-a-keyword-list 2/2 38/38 fixtures green · machine-verified
- 136
- workflows
- 108
- tools mapped
- $80/mo
- in subs replaceable
Popular workflows
View all →Buzz + Hermes over ACP: prove channel scope bounds what an agent reads, because signing is provenance not authorization
Run Hermes as an ACP channel member inside Block's Buzz workspace without giving it your whole workspace to read, by proving that Buzz's signed event log is complete provenance yet not authorization, so only scoping the agent to one narrow channel bounds what it can read.
n8n as an MCP server: prove each exposed workflow is one narrow tool behind its own token
Expose n8n workflows to an agent through MCP Server Triggers without handing it your whole toolbox, by proving each agent-callable trigger is one narrow workflow behind its own bearer token with no wildcard-HTTP or delete-capable node, so a leaked token or a prompt injection is bounded.
QM: prove the destructive-action denials hold in every security posture, even the loosest
Run YC's company-wide QM agent with one org-wide security posture, and prove the predeclared hard denials (recursive delete, destructive SQL, mass delete) are refused in every posture including the loosest, so loosening the posture only relaxes approvals, never the destructive-action guardrails.
pgvector on Postgres you already run: prove you picked the right distance operator
Use pgvector in the Postgres you already run instead of standing up a dedicated vector database, and prove the distance operator you query with (<-> L2, <=> cosine, or <#> inner product) matches your embeddings, so your semantic search doesn't silently rank the wrong rows first.
One AGENTS.md, no drift: prove CLAUDE.md is a real symlink and the generated files are in sync
Keep one AGENTS.md as the single source of agent rules, symlink CLAUDE.md to it, and prove with CI that the symlink is committed as a symlink (not a Windows-materialised copy) and that any generated per-tool file byte-matches a fresh regeneration from the source, so nothing silently drifts.
One shared memory for every coding agent: prove the configs actually point at the same server
Wire a Markdown memory MCP server (Basic Memory or an Obsidian MCP) into Claude Code, Cursor and Cline, and prove with CI that all three resolve to one server, that a write-the-memory house rule exists, and that the vault is under git before any agent gets write access.
Built a workflow?
Get it machine-verified and earn a shareable badge you can link from your post. We run the setup through our CI and verify what passes.
Request verification →Newsletter · Tue · Thu · Sat
WebAfterAI
AI agents, automation, and the next internet.
Three issues a week, Tuesday, Thursday, and Saturday, on what builders are actually shipping. From the r/WebAfterAI community.