Use Falsify Workflow Packs
Getting Started ? Use locally & BYOK
Workflow packs are local, repeatable review instructions?not hosted services and not proof by themselves. Each pack tells an agent what evidence to request, how to challenge a claim, and how to format a verdict. Keep the resulting evidence and verdict artifact with your work.
Available packs
| Pack | Use it when |
|---|---|
| Brooks-Lint (L0 Framework) | Structural decay / auditability review before adversarial attack; product L0 layer. See Brooks-Lint. |
| Deployment Claim Review | A deploy sounds successful but you need evidence of the target state. |
| AI PR Review | A human or agent PR claims work is complete. |
| Research Report Audit | A memo may rely on stale, cherry-picked, or unsupported evidence. |
| Agent Safety Check | An agent says it finished a consequential task. |
| Live Production Gate | Live/cron restore or production-shaped claims (pattern export). |
Note: Installing the Brooks-Lint pack is not Claiming Falsify. Claim-bearing authority still exits through python -m falsify review (default L0) or python -m falsify brooks. falsify lint is a markdown tag/blocker check only — not Brooks-Lint.
Install in Claude Code
- Copy one folder from
skills/into a project or user skills location, for example.claude/skills/falsify-deployment-claim/. - Confirm the folder contains
SKILL.md. - Reload or restart your host if it requires it.
- Invoke the pack with the claim and the raw artifacts requested by its input template.
Install in Cursor
- Copy a folder from
skills/into.cursor/skills/<skill-name>/or your Cursor user skills location. - Confirm the folder contains
SKILL.md. - Let the host load it when the task matches, then provide the requested evidence.
No Falsify API key is required to install a pack. A live model-backed review still uses your provider key or a locally authenticated agent CLI.
What a pack does not do
A pack does not automatically inspect your cloud account, run a production gate, or turn an agent's answer into evidence. Use it to structure the review; use the CLI or your own verification commands to generate and retain artifacts.