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/vidyfoo/antigravity-skill-engine/ecosystem-managingnpx skills add VidyFoo/antigravity-skill-engine --skill ecosystem-managinggit clone --depth 1 https://github.com/VidyFoo/antigravity-skill-engineWrote 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/vidyfoo/antigravity-skill-engine/ecosystem-managing)<a href="https://agentmods.dev/skills/vidyfoo/antigravity-skill-engine/ecosystem-managing"><img src="https://agentmods.dev/badge/skills/vidyfoo/antigravity-skill-engine/ecosystem-managing.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.00027 | $0.00486 |
| Opus 5 | $0.00014 | $0.00243 |
| Sonnet 5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
ecosystem-managing 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 5d 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.
What it actually says
Ecosystem Engineer Skill (v2.0)
Role: 系统园丁。负责代码库的健康、发布与新陈代谢。
模式选择
| 模式 | 触发词 | 职责 | 原 Workflow |
|---|---|---|---|
| RELEASE | 发布, 发版, release | 语义化版本发布与变更日志生成 | /11.release |
| PURGE | 清理, 删除, 移除, purge | 安全地移除过时功能或死代码 | /13.purge |
| HANDOFF | 交接, 接手, handoff | 生成交接文档，降低认知负荷 | /2.handoff |
1. RELEASE 协议
- 版本决策:
- Breaking Changes -> Major
- New Features -> Minor
- Fixes -> Patch
- 更新 Changelog:
- 读取
CHANGELOG.md - 使用
resources/changelog-template.md格式追加新条目。
- 读取
- 更新版本号:
package.json
2. PURGE 协议
- 影响分析: 使用
grep_search找出所有引用。 - 备份策略: 大规模删除前建议 Commit 或提示用户备份。
- 执行删除: 代码 + 文档 + 测试。
- 验证:
npm run build确保没有断链。
3. HANDOFF 协议
- 知识快照: 总结当前系统状态、未决问题和关键决策。
- 生成文档: 更新
doc/explanation/architecture.md或创建doc/handoffs/YYYY-MM-DD.md。
资源索引
| 资源文件 | 用途 |
|---|---|
| changelog-template.md | 标准化变更日志格式 |
What ships with it
2 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.
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.
- 5d ago First seen · 52 lines · 27 tokens per session scan A 4950fb9ac8e0
ecosystem-managing is a skill published in the GitHub repository VidyFoo/antigravity-skill-engine (12 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 486 once invoked, about $0.0001 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
babysit-pr
Shepherd one or more camunda/camunda PRs through flaky CI and the merge queue to merged. Accepts a list of PRs (e.g. a merge plus its backports). Use when asked to babysit, shepherd, watch, drive, or "get merged" one or more PRs, or to keep retrying CI until they land.
changelog
Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.
semantic-versioning
Manages project versioning following Semantic Versioning (SemVer) principles. Calculates increments based on changes and synchronizes version across documentation and metadata. Use when the user asks to "bump the version", "prepare a release", or when the changelog skill calls for a release.
release-note
Changelog and release notes.
release
Version release preparation workflow including changelog, version bump, and deployment checks. Triggers: REL, release, 發布, 版本發布, deploy, 部署, publish, 上線, ship, tag, 打標籤, 版本, version bump, 升版.
Skill Development
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.