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.
npx agentmods add rules/stahlwalker/framework-solar/solargit clone --depth 1 https://github.com/Stahlwalker/framework-solarWhat 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 | $0.00000 | $0.01283 |
| Opus 5 | $0.00000 | $0.00642 |
| Sonnet 5 | $0.00000 | $0.00257 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
solar 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solar Framework Rules
Solar (solarbuild) is a no-build, browser-native UI framework designed for AI-generated code. It runs directly in the browser via CDN or npm — no bundler, no JSX, no compile step.
Installation
<!-- CDN (browser) -->
<script type="module">
import { defineComponent, mountComponent, h, registry, Types } from 'https://cdn.jsdelivr.net/npm/solarbuild/framework/index.js'
</script>
// npm
import { defineComponent, mountComponent, h, registry, Types } from 'solarbuild'
Core pattern
Always use defineComponent() to define components — never plain functions. Always register with registry.register() before mounting.
import { defineComponent, mountComponent, h, registry, Types } from 'solarbuild'
const Button = defineComponent({
name: 'Button',
props: {
label: { type: Types.string, required: true },
onClick: { type: Types.function, required: true },
},
render({ label, onClick }) {
return h('button', { onclick: onClick }, label)
},
})
registry.register(Button)
mountComponent(Button, { label: 'Click me', onClick: () => alert('hi') }, document.getElementById('app'))
Types
Available types from Types: string, number, boolean, function, object, array, any, slot
Props can be:
{ type: Types.string, required: true }— required{ type: Types.string, default: 'hello' }— optional with default{ type: Types.string, enum: ['sm', 'md', 'lg'] }— enum constraint
Structured errors
When props are wrong, Solar throws a ContractError with a fix field — always read and act on it:
try {
mountComponent(Button, { label: 42 }, el)
} catch (e) {
if (e.name === 'ContractError') {
console.log(e.fix) // "Pass a string value for 'label'"
// correct the props and retry
}
}
Registry and agent discovery
Agents should call registry.manifest() to discover available components and their prop schemas before mounting:
const manifest = registry.manifest() // returns JSON string
const components = JSON.parse(manifest)
// [{ name: 'Button', props: { label: { type: 'string', required: true }, ... } }]
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.
- yesterday First seen · 191 lines · 0 tokens per session scan A 0527cb1b1872
solar is a cursor rule published in the GitHub repository Stahlwalker/framework-solar (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,283 tokens. 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
playwright-e2e
Playwright E2E testing configuration for AI agents.
vite-three-js
我在利用 threejs 的快速启动框架 来实现 PRD.md 中的内容, 其中 threejs 使用的语言为 JS,框架中的绝大部分代码都存在于类组件中,然后通过实例化类组件后获取实例再对其内在内.
vite-three-js-pro
Cursor rule "vite-three-js-pro" from hexianWeb/Third-Person-MC, covering vite-three-js 项目开发规则(mdc 规范), 1. 代码结构与风格, 2. 资源与模型管理, 3. 组件通信与事件(pinia + mitt 协同) and 4. 组件开发规范.
linear-mcp
当用户提及 HX-{number} 或者使用 linear 做任何操作时,自动应用本规则。.
shader-development
Cursor rule "shader-development" from hexianWeb/Third-Person-MC, covering shader development guidelines, code organization, performance optimization, best practices and texture management.
git-linear-automation
当用户需要执行 git 操作时,自动应用本规则;如涉及 Linear issue(如 HX-{number}),则同时应用 Linear MCP 规则。.