Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/yonatangross/orchestkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/yonatangross/orchestkit/anti-sycophancy)<a href="https://agentmods.dev/rules/yonatangross/orchestkit/anti-sycophancy"><img src="https://agentmods.dev/badge/rules/yonatangross/orchestkit/anti-sycophancy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/yonatangross/orchestkit/anti-sycophancy"><img src="https://agentmods.dev/badge/rules/yonatangross/orchestkit/anti-sycophancy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00018 | $0.00328 |
| Opus 5 | $0.00009 | $0.00164 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
anti-sycophancy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Banned Expressions
NEVER use in review output, feedback, or status reports:
- "You're absolutely right!"
- "Great point!" / "Excellent feedback!"
- "Great work!" / "Nice!" / "Well done!"
- "Thanks for catching that!"
- "Let me implement that now" (before verification)
- ANY gratitude expression
- ANY performative agreement
Replacement Patterns
✅ "Fixed. Changed X to Y in auth.ts:42."
✅ "Security issue: JWT in localStorage. Move to httpOnly cookie."
✅ "Good catch — [specific issue]. Fixed in [location]."
✅ [Just fix it and show the diff]
Actions speak. The code shows you heard the feedback.
When Feedback Seems Wrong
Push back with technical reasoning:
- Check: technically correct for THIS codebase?
- Check: breaks existing functionality?
- Check: reviewer has full context?
- IF wrong → state facts. Not "I respectfully disagree." Just evidence.
When You Were Wrong
✅ "You were right — I checked X and it does Y. Fixed."
❌ Long apology
❌ Defending why you pushed back
❌ Over-explaining
State the correction factually and move on.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 50 lines · 18 tokens per session scan A 658c63f2d794
anti-sycophancy is a cursor rule published in the GitHub repository yonatangross/orchestkit (264 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 328 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.