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/Lawofall/AgentCoreWrote 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/lawofall/agentcore/desktop-layout)<a href="https://agentmods.dev/rules/lawofall/agentcore/desktop-layout"><img src="https://agentmods.dev/badge/rules/lawofall/agentcore/desktop-layout/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/lawofall/agentcore/desktop-layout"><img src="https://agentmods.dev/badge/rules/lawofall/agentcore/desktop-layout.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.00000 | $0.01931 |
| Opus 5.5 | $0.00000 | $0.00772 |
| Sonnet 5.5 | $0.00000 | $0.00386 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
desktop-layout 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 4d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 4d ago Changed a356a6521022
- 11d ago Changed 00fab4d9a1a2
- 24d ago Changed 1683ea3fef0d
- 25d ago Changed · +16 lines 488fec5abf70
- 1mo ago Changed dbe807166523
- 1mo ago Changed · -1 lines 560b9e191d07
- 1mo ago Changed · +1 lines b4ccb9be8fb4
- 1mo ago Changed · +10 lines 025d45333e65
- 1mo ago First seen · 29 lines · 0 tokens per session scan A 50cf50bd87ca
desktop-layout is a cursor rule published in the GitHub repository Lawofall/AgentCore (89 stars, last pushed 3d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,931 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-30.
Other cursor rules, from other repositories
design
All tasks related to updating frontend components, CSS, and general styling.
frontend-theme-guidelines
Frontend theme-system rules for NekroAgent, covering the theme architecture, core file structure, design principles, and usage guidance. A theme system controls shared visual choices such as colors, typography, and layouts.
ui-and-styling-rule
Guidelines for UI and styling, focusing on Tailwind CSS and Shaden UI best practices.
antd-design-system
A maintenance guide for interfaces built with Ant Design, a React component library, and antd-style, its styling companion. The description only says it applies to existing components.
ui-designer
UI designer rules — theme variables, color usage, no literal hex in app code.
figma-shadcn-ui-generate
1:1 Figma design implementation using shadcn/ui, Tailwind CSS, and React. Apply when implementing or converting Figma designs to code, building UI from design specs, or when user mentions Figma URLs or design-to-code.