SKILLEMALL.ai

DC implementing-honeytokens-for-breach-detection

Deploys canary tokens and honeytokens (fake AWS credentials, DNS canaries, document beacons, database records) that trigger alerts when accessed by attackers. Uses the Canarytokens API and custom webhook integrations for breach detection. Use when building deception-based early warning systems for intrusion detection.

Not recommendedcritical or high security findings · low grade D
mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 4 files · 1 script body ≈ 411 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Deploys canary tokens and honeytokens (fake AWS credentials, DNS canaries, document beacons, database records) that trigger alerts when accessed by attackers.

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

AnalyzerAWSSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
D
76/100
safety, quality, tests
Safety 60%
76
Quality 40%
75
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Exfiltration
If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 3

  • high Exfiltration exfil-read-secret-files SKILL.md:81
    Reads credential / secret files
    with open("/opt/backup/.aws/credentials", "w") as f:
Medium and low: 2
  • medium Exfiltration exfil-read-secret-files scripts/agent.py:134
    Reads credential / secret files (quoted — discussed, not commanded)
    {"type": "aws_credentials", "location": "/opt/backup/.aws/credentials",
    quoted
  • low Exfiltration exfil-webhook-url references/api-reference.md:13
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    "webhook_url": "https://hooks.slack.com/...",  # optional
    placeholder

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • note frontmatter-key unknown frontmatter key "domain"
  • note frontmatter-key unknown frontmatter key "subdomain"
  • note frontmatter-key unknown frontmatter key "nist_csf"
  • note frontmatter-key unknown frontmatter key "mitre_attack"

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 13 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 411 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 319: enough signal without eating the budget
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 13 items
  • +4Has examples (2 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.