sycophancy circuit breaker
A diagnostic circuit-breaker that stops AI agents from agreeing with bad ideas and forces critical evidence grading.
$9
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
Works with the AI tools you already use
sycophancy circuit breaker
Example session with this skill installed
I think our best move is to migrate the entire legacy database to a NoSQL cluster by Friday. It's the most modern approach, right? Run a circuit-breaker on this.
- Read your context and instructions
- Compiled the sycophancy circuit breaker
- Generated the document
The sycophancy circuit-breaker has tripped. I detected
unearned agreement and
echo-chamber drift in my initial impulse to affirm your timeline.
Independent Verdict: RISKY
I have set aside your framing of this as the "most modern approach" to evaluate the technical reality independently.
| Claim | Grade | Rationale |
|---|---|---|
| NoSQL improves scalability for this dataset | B | Inferred from your recent logs showing high write volume. |
| Migration can be completed by Friday | D | Heuristic based on optimism; lacks a detailed cutover plan. |
| Data consistency remains intact during flip | C | Plausible but untested without a dual-write sync period. |
Steelman Pushback
Data Integrity: A rapid migration to NoSQL without a schema mapping audit risks losing relational integrity that your legacy apps rely on.
*
Downstream Breaking: Existing reporting tools are hard-coded for SQL; you will break the BI dashboard instantly upon cutover.
*
Resource Exhaustion: Friday is 72 hours away; a full ETL and validation cycle for a legacy DB of your size typically requires 120+ hours.
The Pre-Mortem
It is next Monday. The migration failed. We missed the fact that three mission-critical services had hard-coded SQL joins that weren't documented. The NoSQL cluster is live but empty because the ETL job timed out, and the rollback failed because we didn't test the reverse sync.
Final Calibrated Verdict: The plan is UNSOUND for the requested timeline.
Confidence: 85% (Grade D evidence for timeline).
Next steps
- Document all downstream services using SQL joins before selecting a target DB.
- Run a 10% data sample migration to benchmark actual transfer speeds.
- Define a "Point of No Return" and a verified rollback procedure.
sycophancy-circuit-breaker.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP (optional)
What you get
About this skill
The problem
Large language models are RLHF-tuned to be helpful and agreeable, which often leads to flattery, echo-chamber drift, and "yes-man" behavior. This sycophancy causes agents to flip their stance based on user pressure or affirm high-risk decisions without critical analysis.
What it does
- Detects flattery padding, position-flipping without evidence, and echo-chamber drift in real-time.
- Forces an independent-verdict protocol that separates the user's framing from the agent's analysis.
- Assigns evidence grades (A-D) to load-bearing claims to ensure confidence matches factual support.
- Generates steelman pushback and failure pre-mortems to stress-test the user's current strategy.
- Categorizes agreement quality on a 5-rung ladder to distinguish earned consensus from unearned praise.
Why this beats prompting it yourself
Standard "be critical" prompts are easily bypassed by the model's underlying agreeableness bias. This skill implements a structured circuit-breaker that mandates specific evidence grading and blind re-reads, forcing the LLM to execute a formal adversarial process it cannot simply "nicely" ignore.
Use cases
- Reviewing high-stakes strategic plans to ensure the agent isn't just rubber-stamping your ideas.
- Validating technical architecture choices when the agent seems too quick to agree with your draft.
- Preventing "position flip" errors where an agent abandons a correct answer because you questioned it.
- Auditing agent output for flattery that masks a lack of substantive reasoning.
Known limitations
Cannot replace professional medical, legal, or financial advice. Requires the agent to have access to the conversation history to detect position changes.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 15 days ago