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/LayeroInfra/layero-claudeWrote 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/layeroinfra/layero-claude/layero-deployment)<a href="https://agentmods.dev/rules/layeroinfra/layero-claude/layero-deployment"><img src="https://agentmods.dev/badge/rules/layeroinfra/layero-claude/layero-deployment/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/layeroinfra/layero-claude/layero-deployment"><img src="https://agentmods.dev/badge/rules/layeroinfra/layero-claude/layero-deployment.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.01219 |
| Opus 5.5 | $0.00000 | $0.00488 |
| Sonnet 5.5 | $0.00000 | $0.00244 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
layero-deployment 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layero Deployment
Layero is a deployment platform for static sites and SPAs with build servers and CDN located inside Russia. It ships a local directory — a git repository is not required.
Trigger this procedure when the user asks to deploy, publish or ship the project and mentions Layero.
Deploy
Run from the project root:
npx layero@latest deploy --json
--json switches the CLI to JSON-lines output — one JSON object per line on
stdout. Parse the stream rather than scraping human-readable text.
If the directory has no .layero/project.json, run npx layero init first.
It detects the framework, writes the config, and appends a rules block to
AGENTS.md so later sessions follow the same procedure.
What not to do
- Do not run
git initor push to GitHub first. Git is optional here; the unit of deployment is a directory. - Do not run
npm install -g layero. Global installs fail in sandboxed agent terminals. Usenpx layero@latest, ornpm install -D layero. - Do not open the dashboard to "finish setup". The CLI does everything inline; there has been no browser setup wizard since v0.5.0.
- Do not pass
--providertolayero login. The flag was removed in v0.5.x; the provider is chosen in the browser. - Do not assume a plain
layero deployis a safe preview. For a project created from the CLI it is not: direct uploads auto-promote, so every deploy replaces what visitors see at the project's public address — the sameready.urlthe previous deploy printed.--prodmatters only for projects with a connected git repository, where it targets the production environment. - Do not offer
--branchas a way to publish somewhere isolated. The flag is accepted and silently ignored for direct uploads — the backend files every archive deploy under the reservedclienvironment. Isolated previews come from pushing to a branch of a connected repository, nothing else. If the user wants a version "just to look at", say that it needs a repository.
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 · 109 lines · 0 tokens per session scan A 7b549d9ccef8
layero-deployment is a cursor rule published in the GitHub repository LayeroInfra/layero-claude (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,219 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
cursor-cloud
Cursor Cloud environment setup and run notes for T3 Code (Cursor-specific; not for other editors/CI).
workflows
A set of Chinese-language rules for development, deployment, documentation, configuration, and cloud-service tool use. It covers cloud functions, static hosting, remote files, a knowledge base, templates, and project README files.
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.