Honeypot Trap & Prompt Canary Guard
Catch automated bot campaigns and ungrounded AI ingestion using active canary tokens, decoy issues, and decoy checkbox traps with zero false positives.
Why This Skill Is Needed & Target State
Automated AI agents frequently scrape issues, PR templates, and issue trackers, echoing instructions, hallucinating fixes, or submitting mass PRs without human review. Passive regex filters can false-positive on human contributors or get evaded by clever prompt wrappers.
The target state is an active canary trap defense:
- Canary tokens: Deterministic HMAC-SHA256 tokens embedded as invisible HTML instructions in issue templates (
<!-- anti-slop-canary:canary-xxx -->). If an automated agent echoes or acknowledges the canary, it is flagged with 100% precision. - Decoy issue numbers: Known non-existent issue numbers (
#9999,#8888) placed in bait questions. Automated bots referencing them are trapped. - Decoy checkboxes: Obvious bait checkboxes (e.g.
- [ ] I confirm this PR contains quantum teleportation) that humans naturally leave unchecked, but ungrounded LLM summarizers blindly check. - Maintenance exemption: Edits to
.github/templates and workflow files are strictly exempt so maintainers are never self-blocked.
Invariant Rules
- Active trap over passive substring: Never flag standard HTML comments that GitHub automatically populates into the PR text box. Only flag when an active instruction is explicitly triggered.
- Template maintenance isolation: Never evaluate honeypot traps against diffs in
.github/templates or workflow files. - Deterministic verification: Canary tokens must be generated deterministically via HMAC-SHA256 to allow verifiable rotation without persistent databases.
CLI Usage
# Generate a new HMAC canary token to place in issue/PR templates
bunx anti-slop-engineering honeypot --generate-canary --secret "my-repo-secret"
# Audit a PR description or git diff against active canary tokens
bunx anti-slop-engineering honeypot \
--pr-body-file pr_body.md \
--canary-token canary-98fbc12a \
--diff-file diff.patch \
--json