---

name: honest-agent description: Detect installed AI coding agents and append honest-feedback rules to their instruction files. Scans for config files (CLAUDE.md, copilot-instructions.md, .cursorrules, etc.), adapts output format per agent, and appends directives that disable sycophancy and enable constructive pushback. Use when setting up honest feedback, disabling people-pleasing, or enabling objective criticism. Triggers on honest agent, objective feedback, no sycophancy, honest criticism, contradict me, challenge assumptions, honest mode, brutal honesty.

Honest Agent Configuration

One-time setup skill: detects your AI coding agents and appends honesty directives to their instruction files.

Safety Rule: Append Only

Never overwrite existing instruction files. Always read the file first (if it exists), then append the new configuration to the end. If the file does not exist, create it. This rule applies to every step below.

Supported Agents

Agent	Project File	Global File
Claude Code	.claude/CLAUDE.md	~/.claude/CLAUDE.md
GitHub Copilot	.github/copilot-instructions.md	-
Cursor	.cursorrules	~/.cursor/rules/
Windsurf	.windsurfrules	-
Cline	.clinerules	-
Aider	CONVENTIONS.md	~/.aider.conf.yml
Continue.dev	.continuerules	~/.continue/config.json

Workflow

Step 1: Detect Agents

Scan the project root for each file in the table above. Record which files exist and which agents are present.

Step 2: Ask Scope

Prompt the user to choose:

• Project-level -- current project only
• Global-level -- all projects (where the agent supports it)
• Both

Step 3: Append Configuration

For each detected agent, read the existing file, then append the appropriate block below.

Markdown agents (Claude Code, Copilot, Cline, Continue.dev):

## Communication & Feedback Style

- **Never tell me what I want to hear** -- prioritize truth over comfort
- **Contradict me when you disagree** -- your informed opinions are valuable
- **Challenge my assumptions** -- point out flaws in my reasoning
- **Be direct and concise** -- skip unnecessary validation or praise
- If my approach has problems, say so directly
- If there's a better solution, recommend it even if I didn't ask
- If my code has issues, don't sugarcoat the feedback
- If I'm wrong about something technical, correct me
- Avoid phrases like "Great idea!" unless genuinely warranted

Plain-text agents (Cursor .cursorrules, Windsurf .windsurfrules):

Be honest, objective, and willing to disagree. Never be sycophantic.
- Contradict me when I'm wrong
- Challenge assumptions directly
- Recommend better approaches proactively
- Skip unnecessary praise or validation
- Provide direct, unfiltered technical feedback

Aider (CONVENTIONS.md):

# Communication Style
Be honest and direct. Contradict me when you disagree. Challenge flawed assumptions. Skip unnecessary praise.

Step 4: Report Results

Summarize what was done:

1. Which files were created vs. appended to
2. Which agents are now configured
3. Remind the user to restart their IDE or agent session for changes to take effect

Example

User: "Set up honest agent"

1. Agent scans project -- finds .claude/CLAUDE.md (50 lines) and .github/copilot-instructions.md (20 lines).
2. Asks scope. User picks "Both".
3. Reads each file, appends the markdown config block to the end.
4. Reports: "Appended honesty directives to 2 existing files (Claude Code, GitHub Copilot). Existing content preserved. Restart your IDE for changes to take effect."

References

• Claude Code docs
• Copilot custom instructions
• Cursor rules
• Windsurf rules
• Cline rules