flake-to-fact

Install

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.

Security

Grade A, and why

flake-to-fact 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 2d 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.

plugins/flake-to-fact/.claude-plugin/plugin.json · 13 lines

What it actually says

{
  "name": "flake-to-fact",
  "description": "Replace vague flaky-test language with the narrowest evidence-supported classification for test, build, deployment, performance, security, and CI failures. Separates recurrence from cause, records confidence, and requests a specific diagnostic when evidence is insufficient.",
  "version": "1.0.0",
  "author": {
    "name": "Lance Willett"
  },
  "license": "MIT",
  "skills": [
    "./skills/flake-to-fact"
  ]
}

Changes

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.

Related

Other plugins, from other repositories