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 agentmods add skills/vixues/leagent/skill-packagernpx skills add vixues/LeAgent --skill skill-packagergit clone --depth 1 https://github.com/vixues/LeAgentWrote 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/vixues/leagent/skill-packager)<a href="https://agentmods.dev/skills/vixues/leagent/skill-packager"><img src="https://agentmods.dev/badge/skills/vixues/leagent/skill-packager.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.00659 |
| Opus 5 | $0.00044 | $0.00329 |
| Sonnet 5 | $0.00017 | $0.00132 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
skill-packager 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill packager
Help the user create, package, and install Agent Skills v1.0 bundles.
When to use
- User finished a doc, workflow, or code and wants it reusable as a skill.
- User pastes an https:// link to a
.zip/.tar.gzskill bundle to install. - User wants a .zip to import into Cursor (
~/.cursor/skills/or.cursor/skills/) or another agent.
Authoring layout
- One directory per skill: directory name must equal the
namefield inSKILL.mdfrontmatter (kebab-case). - Put long prose in
references/orassets/; keepSKILL.mdconcise with links to those files. - Optional
scripts/for helpers; script execution may require server env flags—document that.
Tools (LeAgent)
| Goal | Tool |
|---|---|
| Validate + zip a folder | package_skill with skill_directory (optional output_path) |
| Install from URL | install_skill with source_type: url, url, optional sha256 |
| Install from registry | install_skill with source_type: registry, registry_skill_name |
| Install from project folder | install_skill with source_type: workspace, workspace_path, target_skill_name |
| Install from uploaded archive | install_skill with source_type: uploaded_archive, file_id |
After installation, use load_skill with the returned skill name to pull instructions.
Cursor / desktop import (manual)
If the user only needs Cursor (not LeAgent runtime): give them the zip from package_skill and instruct them to extract so one top-level folder skill-name/ contains SKILL.md, then copy that folder into %USERPROFILE%\.cursor\skills\ or the project’s .cursor/skills/. Do not place skills in ~/.cursor/skills-cursor/ (reserved for built-ins).
Quality checklist
-
descriptionin frontmatter states what the skill does and when to use it (third person). - Directory name matches
nameinSKILL.md. - Run
package_skillbefore sharing the zip; fix validation errors if any.
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 First seen · 48 lines · 87 tokens per session scan A 0b6629a1719c
skill-packager is a skill published in the GitHub repository vixues/LeAgent (216 stars, last pushed 23d ago), licensed Apache-2.0. It adds 87 tokens to every session and 659 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the /rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
using-rn-dev-agent
Entry point for the rn-dev-agent plugin. Maps user intent to the right command, agent, or skill. Use at the START of any React Native development conversation. Triggers on "I want to build", "build a feature", "add a feature to the app", "test this", "something is broken", "fix the crash", "help with my React Native…
creating-actions
This skill should be used when the user asks to "create an action", "save this flow as an action", "make this replayable", "record a reusable action", "author a Maestro flow as an action", "add a login/setup action", or when a verified UI walk should be persisted under .rn-agent/actions/ so future sessions can replay…
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…