control-effectiveness-vs-existence SKILL.md skillA
control-effectiveness-vs-existence from annatchijova/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add annatchijova/skills/control-effectiveness-vs-existence@git:20260825.8500180Pins git:20260825.8500180 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- annatchijova/skills
- Path
control-effectiveness-vs-existence/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260825.8500180, committed Aug 25, 2026
- Size
- 7,822 bytes
- Repository stars
- 9
- License
- a license file GitHub does not identify
Distinguish a control that exists from a control that works — because compliance attests existence ("MFA is enabled") while security requires effectiveness ("MFA that cannot be phished or bypassed on this path"), and the checkbox is passed by the presence of the control, not by its resistance to the threat it names. Use whenever a control is being claimed, audited, or trusted: "we're compliant", "we have MFA / EDR / a WAF / DLP", "we passed SOC2", "the control is in place…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Control Effectiveness vs Existence A control that exists is not a control that works, and the entire compliance apparatus is built to attest the first while implying the second. "MFA is enabled" passes the audit; whether that MFA can be phished, SIM-swapped, prompt-bombed, or simply bypassed on a legacy authentication path is a different question that the checkbox never asked. Compliance measures *presence*; security measures *performance against a threat*; and the gap between them is where breached-but-compliant organizations live. The reframe: **a control is a claim that a specific threat is stopped, and a claim is tested by trying to defeat it, not by confirming it is switched on.** "We have a WAF" is existence. "The WAF blocks the injection payloads that reach this endpoint, and here is the test that shows it" is effectiveness. Only the second is a security statement. The failure modes: - **The checkbox that passes on presence.** "Do you have anti-malware? Y/N." Yes. The control is EDR in audit-only mode that has never blocked anything, and the box is green. Compliance is satisfied; the threat is not addressed. …
Read the whole file at its exact version.
How to install
mdr add annatchijova/skills/control-effectiveness-vs-existence@sha256:576481210a86a66eThe line at the top of this page pins the label git:20260825.8500180, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_52gk5x6yt33cnbsd)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 25, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7822 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
annatchijova/skills · 9 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_52gk5x6yt33cnbsd GET https://markdownregistry.com/api/v1/resolve?ref=annatchijova/skills/control-effectiveness-vs-existence GET https://markdownregistry.com/api/v1/blob/576481210a86a66e64c38464b1b4966693fc57c80ae4302fc1f07885e3da24c3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.