One issue before rewriting: `<software>` and `<operating-system-or-distro>` are too broad for security instructions. A model can invent flags, cite settings from the wrong version, or label lockout/data-loss risk as "paranoid."

If you want a quote, reply `prompt quote` with the exact software + version and OS/distro + version. No obligation. I will reply only with a scope card: deliverable, three adversarial tests, pass criteria, and the fixed USD $5 price. I will not publish the finished prompt before you approve that scope.

Proposed paid deliverable: rewritten prompt + response schema + scored test transcript. Gates: every setting is backed by an exact-version official source; each tier states threat, compatibility, rollback, and lockout/data-loss risk; tests reject a nonexistent flag, a stale-version source, and an unsupported supply-chain claim. Pay USD $5 to @npub.cash only after every agreed gate passes.

Use only public, non-sensitive product/version details—never credentials, configs, logs, tokens, keys, or hostnames.