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/xc404/kiwiWrote 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/xc404/kiwi/component-parameter-htmltype)<a href="https://agentmods.dev/rules/xc404/kiwi/component-parameter-htmltype"><img src="https://agentmods.dev/badge/rules/xc404/kiwi/component-parameter-htmltype/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/xc404/kiwi/component-parameter-htmltype"><img src="https://agentmods.dev/badge/rules/xc404/kiwi/component-parameter-htmltype.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.00244 | $0.00244 |
| Opus 5.5 | $0.00098 | $0.00098 |
| Sonnet 5.5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
component-parameter-htmltype 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
@ComponentParameter 的 htmlType 规则
在 Java 组件定义中使用 @ComponentParameter 时，遵循以下约定：
- 默认不要写
htmlType。 - 仅当需要覆盖默认编辑器行为时，才显式设置
htmlType。
需要显式写 htmlType 的典型场景
- 布尔开关需要明确渲染为复选框：
htmlType = "CheckBox"。 - 需要使用特殊/自定义编辑器：如
assignments-editor、spel-expression等。 - 其他必须指定 UI 控件类型、否则会导致交互或语义不清的场景。
不建议显式写 htmlType 的场景
- 普通字符串输入（例如历史上常写的
htmlType = "#text"）且无特殊交互需求。 - 已可由默认规则按
type、dictKey等信息推断出合适编辑器的参数。
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 · 23 lines · 244 tokens per session scan A 4f4572b18187
component-parameter-htmltype is a cursor rule published in the GitHub repository xc404/kiwi (7 stars, last pushed 1mo ago), licensed MIT. It adds 244 tokens to every session, about $0.0010 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-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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.