Skip to content

imMamdouhaboammar/anti-slop-engineering / skills/honeypot-trap-guard

honeypot-trap-guard

Verified

Detect automated AI slop and ungrounded LLM ingestion using active prompt canary traps, decoy issue references, and decoy template checkboxes while preventing self-blocking on template maintenance.

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:

  1. 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.
  2. Decoy issue numbers: Known non-existent issue numbers (#9999, #8888) placed in bait questions. Automated bots referencing them are trapped.
  3. 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.
  4. Maintenance exemption: Edits to .github/ templates and workflow files are strictly exempt so maintainers are never self-blocked.

Invariant Rules

  1. 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.
  2. Template maintenance isolation: Never evaluate honeypot traps against diffs in .github/ templates or workflow files.
  3. 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
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall