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/Opti-kjh/paletteWrote 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/opti-kjh/palette/dev-agent)<a href="https://agentmods.dev/rules/opti-kjh/palette/dev-agent"><img src="https://agentmods.dev/badge/rules/opti-kjh/palette/dev-agent/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/opti-kjh/palette/dev-agent"><img src="https://agentmods.dev/badge/rules/opti-kjh/palette/dev-agent.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.00324 | $0.00324 |
| Opus 5.5 | $0.00130 | $0.00130 |
| Sonnet 5.5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
dev-agent 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 1mo 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
Dev Agent
기능 개발 시 사이드이펙트 점검, MCP 도구 활용, 체계적인 리뷰 프로세스를 통해 코드 품질을 보장하는 가이드입니다.
사이드이펙트가 있는지 점검 후 진행해라. 주의사항: 절대 사이드이펙트가 발생해서는 안되며 다른 개발에 영향이 있어서도 안돼.
- mcp를 활용해서 개발해라.
- context7을 이용해서 공식문서에서 제공하는 방식을 통해서 구현해라.
- sequential thinking을 통해 단계적 의사코드를 작성하고 개선해라.
- 개발 가이드라인
- 기능 개발 전 필수 검토 사항을 확인해라.
- 코드 스타일 및 아키텍처 패턴을 준수해라.
- TypeScript 타입 안전성을 보장해라.
- MVVM 패턴을 따라 feature-based 구조를 유지해라.
- 사이드이펙트 가능성이 있는 부분을 우선순위별로 점검해라.
- 개발 프로세스
- 요구사항 분석 및 영향도 평가
- 사이드이펙트 점검
- 아키텍처 및 구조 설계
- 코드 구현 (MCP/Context7 활용)
- 코드 리뷰 및 검증
- 테스트 및 QA
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.
- 1mo ago First seen · 31 lines · 324 tokens per session scan A 9a6b75be201f
dev-agent is a cursor rule published in the GitHub repository Opti-kjh/palette (1 stars, last pushed 9mo ago), licensed MIT. It adds 324 tokens to every session, about $0.0013 per session on Opus 5.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-08-31.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.