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 skills add lovstudio/skills --skill codeex-creatorgit clone --depth 1 https://github.com/lovstudio/skillsWrote 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/skills/lovstudio/skills/codeex-creator)<a href="https://agentmods.dev/skills/lovstudio/skills/codeex-creator"><img src="https://agentmods.dev/badge/skills/lovstudio/skills/codeex-creator/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/skills/lovstudio/skills/codeex-creator"><img src="https://agentmods.dev/badge/skills/lovstudio/skills/codeex-creator.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.00067 | $0.02460 |
| Opus 5.5 | $0.00027 | $0.00984 |
| Sonnet 5.5 | $0.00013 | $0.00492 |
| Haiku 4.5 | $0.00007 | $0.00246 |
Grade A, and why
lov-codeex-creator 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 24d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codeex 插件工坊 · Codeex Plugin Studio
Deliver one self-contained Codeex runtime plugin whose source, permissions, hooks, desired install state, active runtime state, and rollback path are all auditable. Keep every plugin independently installable and uninstallable; never patch another plugin to make the new one work.
Triggers
Activate when
- 用户说“开发一个 Codeex 插件”“把这个能力做成 Codeex plugin”或“原子安装/卸载这个插件”。
- 用户要新增或修改
plugins/<plugin-id>/plugin.json、transformWebview、beforeLaunch、handleControlRequest或 Codeex 插件权限。 - The user asks to “create a Codeex plugin”, “add a Codeex runtime hook”, or “make this Codeex feature independently installable”.
Do not activate when
- 用户要创建 Codex marketplace 的
.codex-plugin/plugin.json、Skill、MCP 或 App；使用 Codexplugin-creator，不要套用 Codeex 运行时契约。 - 用户只要把 Lovinsp 接入普通前端项目；使用
lov-integrate-lovinsp。 - 用户只要修复 Electron/Tauri 的通用 relaunch 行为，而没有 Codeex 插件交付物；使用
lov-electron-app-relaunch。 - 用户只要求启用或停用一个已经存在的插件，且不涉及开发或验证；直接使用 Codeex 插件中心或项目 CLI。
Runtime Context and Profile
Read skill.yaml and resolve the Codeex repository in this order:
- The current request or an explicit
--project-root. - Current project context when it satisfies the Codeex contract.
CODEEX_PROJECT_ROOT.workspace.codeex_rootorskills.lov-codeex-creator.records.codeex_rootfrom the shared Profile.- The current directory when it passes the contract check.
Do not save an inferred path. If the user explicitly says a Codeex root should
be reused in future sessions, persist it with scripts/profile_store.py record --skill-id lov-codeex-creator --path records.codeex_root --value <json-string> --confirm and report the canonical Profile path without echoing private data.
Read references/skill-composition.md before invoking adjacent capabilities.
External Skills are optional artifact handoffs, never runtime dependencies.
Proceed without a question when the repository, plugin boundary, and safe verification path are discoverable. Use AskUserQuestion at most once when a material choice cannot be recovered locally, especially authorization to restart the active Codeex instance or a destructive source-removal request.
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .gitignore 84 B
- cases/cases.json 2.3 KB
- cases/evidence/lifecycle-report.json 859 B
- CHANGELOG.md 1.1 KB
- LICENSE 1.0 KB
- pricing-card.yaml 933 B
- README.md 3.4 KB
- references/atomic-lifecycle.md 3.0 KB
- references/development-loop.md 4.1 KB
- references/plugin-contract.md 4.7 KB
- references/skill-card-standard.md 660 B
- references/skill-composition.md 3.7 KB
- references/user-profile.md 2.7 KB
- references/verification.md 2.7 KB
- scripts/codeex_plugin.py 23 KB runs code
- scripts/profile_store.py 8.3 KB runs code
- scripts/validate_skill.py 25 KB runs code
- skill-card.md 3.5 KB
- skill-card.yaml 6.4 KB
- skill.yaml 1.9 KB
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.
- 24d ago First seen · 266 lines · 67 tokens per session scan A 4823224407f6
lov-codeex-creator is a skill published in the GitHub repository lovstudio/skills (72 stars, last pushed 6d ago), licensed MIT. It adds 67 tokens to every session and 2,460 once invoked, about $0.0003 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-09-26.
Other skills, from other repositories
mongodb-connection
Optimize MongoDB client connection configuration (pools, timeouts, patterns) for any supported driver language. Use this skill when working/updating/reviewing on functions that instantiate or configure a MongoDB client (eg, when calling connect()), configuring connection pools, troubleshooting connection errors…
frontend-testing-debugging
Use when testing, debugging, or making targeted improvements to rendered frontend apps through the Frontend Design Skills or web dev plugin: local dev servers, UI regressions, interaction bugs, console errors, responsive layout, and visual QA. Check whether the Browser plugin is available and use it first when it is…
mongodb-search-and-ai
Guides MongoDB users through implementing and optimizing Atlas Search (full-text), Vector Search (semantic), and Hybrid Search solutions. Use this skill when users need to build search functionality for text-based queries (autocomplete, fuzzy matching, faceted search), semantic similarity (embeddings, RAG…
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
grill-design
Decide a UI design by building several genuinely different working prototypes and comparing them side by side, in rounds, until the choice is locked. Use when asked to "grill the design", "design this screen", "show me options", "prototype some variants", "what should this look like", "I can't decide on a layout".
web-performance-optimization
Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.