deception-signal-quality
Skill9 starsChanged 4 months agoLicence not identifiedView on GitHub
Design deception so that a triggered decoy is a true positive by construction — a honeytoken, honeypot, or canary earns its keep only if nothing legitimate ever touches it, which turns "someone touched it" into signal with a near-zero false-positive rate, the inverse of every noisy detection you own. Use whenever deception is being built or evaluated: "let's plant a honeytoken", "set up a honeypot", "canary tokens", "decoy credentials / files / AWS keys", "tripwire", "we deployed a deception grid", "why is our honeypot noisy", "fake admin account to catch attackers". Sibling of detection-engineering (deception is a detection whose benign-twin rate is engineered to zero) and dual-use-behavior-adjudication (its mirror image: a decoy is built to have no legitimate use, so no adjudication is needed); it judges decoy placement and signal quality. It does not run offensive deception against third parties, and never trusts a decoy whose legitimate-access paths were not eliminated first.
- Reads credentials
In this repository91 other files it gives its agents.
- abductive-engineeringSkill
- acquisition-order-of-volatilitySkill
- agent-trust-boundariesSkill
- alert-triage-economicsSkill
- assume-breach-modelingSkill
- atomic-state-mutationSkill
- attack-surface-triageSkill
- audit-before-patchSkill
- authorization-surface-mappingSkill
- beyond-the-fixSkill
- beyond-the-sinkSkill
- claim-provenance-disciplineSkill
- client-side-trust-boundarySkill
- cloud-architecture-selectionSkill
- cloud-control-plane-reasoningSkill
- codebase-health-assessmentSkill
- concurrency-reasoningSkill
- container-trust-boundarySkill
- containment-under-uncertaintySkill
- control-effectiveness-vs-existenceSkill
- credential-material-triageSkill
- crypto-misuse-reasoningSkill
- data-leakage-huntingSkill
- data-provenance-mappingSkill
- daubert-defensible-writingSkill
- debt-closure-disciplineSkill
- decision-record-disciplineSkill
- dependency-provenanceSkill
- destination-driven-constructionSkill
- detection-engineeringSkill
- deterministic-coreSkill
- diagnosing-bugsSkill
- discriminating-proofSkill
- distributed-write-atomicitySkill
- dont-fall-in-love-with-the-bugSkill
- dual-use-behavior-adjudicationSkill
- exploitability-triageSkill
- falsifiable-testingSkill
- finding-custodySkill
- forensic-logging-designSkill
- forensic-persistenceSkill
- frontend-accessibility-by-constructionSkill
- frontend-component-boundariesSkill
- frontend-performance-budgetsSkill
- frontend-testing-strategySkill
- git-disciplineSkill
- honest-degradationSkill
- honest-technical-oratorySkill
- hypothesis-driven-huntingSkill
- incident-timeline-reconstructionSkill
- intel-source-evaluationSkill
- invariant-huntingSkill
- irreversible-action-gateSkill
- known-defect-dispositionSkill
- language-selectionSkill
- live-contract-compatibilitySkill
- llm-out-of-the-loopSkill
- model-evaluation-disciplineSkill
- non-overwhelming-uxSkill
- oracle-driven-fuzzingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

