EdgeOne Makers Tools is a collection of AI-agent skills and related workflow files for developing and deploying projects on EdgeOne Makers. It covers agent development, deployment, edge and cloud functions, storage, middleware, command-line usage, and project templates. The catalogue entries package these capabilities as skills, rules, instructions, a hook, and a plugin for coding agents.
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/TencentEdgeOne/edgeone-makers-toolsWrote 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/tencentedgeone/edgeone-makers-tools/makers-deploy)<a href="https://agentmods.dev/rules/tencentedgeone/edgeone-makers-tools/makers-deploy"><img src="https://agentmods.dev/badge/rules/tencentedgeone/edgeone-makers-tools/makers-deploy/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/tencentedgeone/edgeone-makers-tools/makers-deploy"><img src="https://agentmods.dev/badge/rules/tencentedgeone/edgeone-makers-tools/makers-deploy.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.00254 | $0.09161 |
| Opus 5.5 | $0.00102 | $0.03664 |
| Sonnet 5.5 | $0.00051 | $0.01832 |
| Haiku 4.5 | $0.00025 | $0.00916 |
Grade B, and why
edgeone-makers-deploy scanned grade B with 2 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 9d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
**How to ask (when asking):** present the choice with the IDE's selection control (e.g. `ask_followup_question`). The option labels deliberately avoid the word "anonymous" — it is jargon and confuses non-technical users. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `curl` to the deploy URL returns 302 → DingTalk SSO login | Preview gateway requires browser-based `eo_token` validation (JS), which `curl` can't do. Open the full `?eo_token=...&eo_time=...` URL in a real browser — it How it starts
The opening of the file, as written. The whole thing — 546 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EdgeOne Makers Deployment Skill
Deploy any project to EdgeOne Makers.
⛔ Critical Rules (never skip)
-
CLI version ≥
1.6.0— reinstall if lower. Versions below1.6.0lack the non-interactive fixes (whoami fail-fast,--jsonoutput) and hang in Agent/CI environments. Never proceed with an outdated version. Anonymous deploy andclaimadditionally require1.6.29— that is a higher, feature-specific floor; see Anonymous Deploy. Do not block a normal authenticated deploy because the CLI is below1.6.29. -
Never truncate the deploy URL — this applies to EVERY mention —
EDGEONE_DEPLOY_URLincludes query parameters (?eo_token=...&eo_time=...) required for access. Without them the page returns 401. Always output the complete URL with full query string. This rule applies to: the primary display, summary tables, footnotes, comparisons, code blocks,present_filescalls — every single occurrence of the URL in your reply. Truncation is any removal of the?and everything after it.❌ WRONG (truncated — will 401):
https://my-app-w9t0lxe8.edgeone.cool✅ CORRECT (full URL):
https://my-app-w9t0lxe8.edgeone.cool?eo_token=abc123&eo_time=1234567890Self-check after writing your reply: scan for every instance of the
.edgeone.cooldomain. Does each one include?eo_token=? If any doesn't, fix it NOW — the user will get a 401. 3a. Prefer--jsonwhen running non-interactively — in Agent/CI/headless contexts, always pass--jsontodeployso the result is a single machine-readable line; no need to scrape colored/\r-animated stdout. See Parse Deploy Output. 3b. Useedgeone whoamito check login status — on CLI ≥ 1.6.0,whoamifails fast (exit 1) when not logged in instead of hanging. If it exits 0, the user is already logged in and-tis not needed. Do NOT checkcat .edgeone/.token— CLI stores credentials in~/.edgeone/<hash>files, not a fixed.tokenpath. -
The deploy URL MUST be placed at the very top of the visible reply body (own line, code block, or heading — not inline, not mid-reply), AND ALSO pinned via
present_files(or the IDE's preview tool) to the side panel. Two UI failures to survive: thinking / reasoning / "深度思考" blocks hide content by default; long replies get auto-folded by IDE chat cards, burying anything placed mid-reply.present_filesis unaffected by chat folding — that's the second, always-visible channel. Complete URL, no truncation (Rule 2). Example format:🌐 Live URL: https://my-project-abc123.edgeone.cool?<auth_query_params>Then append any other notes (console URL, caveats, etc.).
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.
- 9d ago Changed · +4 tokens per session 5fef53ea80bf
- 1mo ago Changed · +2 lines ea7fa22ae23b
- 1mo ago Changed · +154 lines · +52 tokens per session scan A → B 4b9ed1332dea
- 1mo ago First seen · 390 lines · 198 tokens per session scan A b960ad52a60e
edgeone-makers-deploy is a cursor rule published in the GitHub repository TencentEdgeOne/edgeone-makers-tools (1,851 stars, last pushed 2d ago), licensed MIT. It adds 254 tokens to every session and 9,161 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it B with 2 findings (strips warnings and disclaimers, makes network calls). 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
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
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.