TheBotique

adversarial-debate

Cross-vendor adversarial review. WARNING — this sends your brief, and any source files you approve, to a model hosted by a THIRD-PARTY vendor, where it stays in that vendor's session history under their retention terms. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attac

as observed 2026-09-20T22:20:20.811Z
Identifier
adversarial-debate
Source
ClawHub
Version observed
2.4.0
Source repository
not published
Repository observation
No source repository listed
First observed here
2026-08-28T22:06:26.689Z
Observations recorded
4
Installs (reported upstream)
1
Weekly downloads (upstream)
368
Declared license
MIT-0

Observation history

2026-09-20T22:20:20.811Z

Fields that differed: license changelog description latestVersion summary

FieldBeforeAfter
license null "MIT-0"
changelog "Methodology upgrade, not just wording. R1 objections now require a verifiable anchor (file:line, runnable command, citable data) plus a mandatory closing question: what's the fail "Removes the handoff/DeepSeek channel. It launched the external model with permission prompts off, so that model could run commands as the user, which the staging-directory flow co
description "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; every objection carries a verifiable anchor; the defender rules null
latestVersion "2.2.0" "2.4.0"
summary "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; every objection carries a verifiable anchor; the defender rules "Cross-vendor adversarial review. WARNING — this sends your brief, and any source files you approve, to a model hosted by a THIRD-PARTY vendor, where it stays in that vendor's sess
2026-08-31T05:56:02.339Z

Fields that differed: changelog description latestVersion summary

FieldBeforeAfter
changelog "Dropped the keyword list from the description, stopped naming an unpinned install command, and added a 'What this skill sends where' section: the brief is transmitted verbatim to "Methodology upgrade, not just wording. R1 objections now require a verifiable anchor (file:line, runnable command, citable data) plus a mandatory closing question: what's the fail
description "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; the defender rules on every objection; a final round converges o "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; every objection carries a verifiable anchor; the defender rules
latestVersion "2.1.1" "2.2.0"
summary "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; the defender rules on every objection; a final round converges o "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; every objection carries a verifiable anchor; the defender rules
2026-08-29T23:02:09.653Z

Fields that differed: changelog description latestVersion summary

FieldBeforeAfter
changelog "P3 is executable again: the handoff CLI is a public package (uv tool install handoff-cli), and its resume subcommand keeps R1 and R3 on one conversation, which is exactly what thi "Dropped the keyword list from the description, stopped naming an unpinned install command, and added a 'What this skill sends where' section: the brief is transmitted verbatim to
description "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; the defender rules on every objection; a final round converges o "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; the defender rules on every objection; a final round converges o
latestVersion "2.1.0" "2.1.1"
summary "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; the defender rules on every objection; a final round converges o "Cross-vendor adversarial review. Ship a plan, proposal, or design to a model from a DIFFERENT vendor to attack it; the defender rules on every objection; a final round converges o

Correction

If you maintain this extension and believe anything above is inaccurate, request a correction. Corrections are published, and disputed entries are marked as disputed while under review.