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-frameworks)<a href="https://agentmods.dev/rules/tencentedgeone/edgeone-makers-tools/makers-frameworks"><img src="https://agentmods.dev/badge/rules/tencentedgeone/edgeone-makers-tools/makers-frameworks/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-frameworks"><img src="https://agentmods.dev/badge/rules/tencentedgeone/edgeone-makers-tools/makers-frameworks.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.00099 | $0.02568 |
| Opus 5.5 | $0.00040 | $0.01027 |
| Sonnet 5.5 | $0.00020 | $0.00514 |
| Haiku 4.5 | $0.00010 | $0.00257 |
Grade A, and why
edgeone-makers-frameworks 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 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.
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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Frameworks
Which framework a request names decides seven things and nothing else. Every framework runs the same flow — prepare the workspace, write files, install, start the preview, verify — and differs only in the values below.
| Slot | Why it matters |
|---|---|
| Platform adapter | Without it, deploy produces output the platform cannot serve. The preview does not catch this. |
| Scaffold command | One command holds both the structure and a working version set |
| Preview asset-prefix option | The single option that moves framework-emitted asset URLs |
| Build command + output directory | What edgeone.json must declare when it is not the default |
| 404 convention | Different file in every framework |
| Version floor | Below it the platform's adapter or builder does not apply |
| Unsupported features | Generated code that uses one produces a broken site, not an error |
The adapter is a deploy-time contract, not a preview-time one
edgeone makers dev starts the framework's own dev server (it reads devCommand
from edgeone.json, falling back to the dev script in package.json). The platform
adapter takes no part in that. edgeone makers deploy is different: it runs the build
and expects the adapter to have written platform output.
So a project that needs an adapter and does not have one previews perfectly and deploys broken. Every gate is green. This is the single most expensive mistake available in this skill, and it is why the adapter column below comes first.
Five frameworks need one: Astro, React Router, SvelteKit, TanStack Start, Vike. Next.js and Nuxt are supported by the builder directly and need none.
Read the one document for the framework in the request
| Framework | Read |
|---|---|
| Astro | references/astro.md |
| React Router v7 | references/react-router.md |
| SvelteKit | references/sveltekit.md |
| TanStack Start | references/tanstack-start.md |
| Vike | references/vike.md |
| Next.js | references/nextjs.md |
| Nuxt | references/nuxt.md |
| Vite / React / Vue single-page app | references/vite-spa.md |
| Hugo and other static site generators | references/static-generators.md |
| Anything else (Docusaurus, Angular, Gatsby, Hexo, Qwik, Remix, Solid) | references/other-frameworks.md |
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 First seen · 235 lines · 99 tokens per session scan A 8a81ec2b37bf
edgeone-makers-frameworks is a cursor rule published in the GitHub repository TencentEdgeOne/edgeone-makers-tools (1,851 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 2,568 once invoked, about $0.0004 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-10-09.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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).