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/urmzd/dotfiles/sync-ecosystemnpx skills add urmzd/dotfiles --skill sync-ecosystemgit clone --depth 1 https://github.com/urmzd/dotfilesWhat 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.00101 | $0.01424 |
| Opus 5 | $0.00051 | $0.00712 |
| Sonnet 5 | $0.00020 | $0.00285 |
| Haiku 4.5 | $0.00010 | $0.00142 |
Grade A, and why
sync-ecosystem 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 2d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ecosystem Sync
Audit one repository for consistency with the rest of the ecosystem and emit a drift report. To push the report back into the canonical skill store, chain with sync-ecosystem-to-chezmoi (or your equivalent).
Usage: /sync-ecosystem <repo-path>
If no path is given, ask which repo to audit before proceeding.
Principle
Ecosystem conventions evolve. This skill does not enumerate them inline -- that list rots. Instead, it runs an audit loop that pulls the current rules from the skills that own each convention, then reports drift between the target repo and those rules.
Audit Loop
1. Establish repo context
Read whatever identity and manifest files the repo has (README, AGENTS.md, llms.txt, language manifest). From these infer:
- Name and description the identity the rest of the ecosystem should agree with
- Repo type library, CLI, service, website, or something else -- dictates which conventions apply
- Language and build system dictates which
scaffold-<lang>skill to consult
Don't assume any specific file is present. Absence of a file is itself a finding.
2. Pull current conventions
For each convention category, consult the owning skill rather than enumerating rules here:
| Category | Owning skill |
|---|---|
| Required project layout | check-project |
| Community-health files (CODE_OF_CONDUCT, SECURITY, issue forms, PR template) | community-health |
| README structure | write-readme |
| AGENTS.md structure | configure-ai |
| llms.txt structure | create-llms-txt |
| CI/release workflow | setup-ci, sync-release |
| Language-specific scaffold | scaffold-<lang> |
| CLI conventions | build-cli |
| Doc-drift (fsrc, command renames, dead links) | sync-docs (delegate, do not re-implement) |
3. Check drift
Run generic drift checks against what you discovered:
- File presence does the repo have every artifact the owning skills require for this repo type?
- Content currency do listed commands, dependencies, and examples match the current manifest and code?
- Cross-reference agreement do name, description, install command, and version agree across docs and manifest?
- Version discipline does the latest git tag match the manifest version (or match the tagging scheme declared by
sync-release)? - Terminology does usage in the repo match the terms used in this ecosystem's other published skills and docs? Flag divergences; do not auto-rewrite.
- Doc subset for the documentation-specific portion of the audit (fsrc drift, dead internal links, stale commands), invoke
sync-docsinstead of re-implementing the checks.
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.
- 2d ago First seen · 136 lines · 101 tokens per session scan A 8d4af1452d8d
sync-ecosystem is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 101 tokens to every session and 1,424 once invoked, about $0.0005 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-31.
Other skills, from other repositories
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
esm
Comprehensive toolkit for EvolutionaryScale protein language models including ESM3 (generative multimodal design across sequence, structure, and function) and ESM C (efficient embeddings). Use for protein sequence/structure/function tasks, inverse folding, embeddings, variant design, and ESMFold2 structure prediction…
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
mcp-notion-usage-guide
MCP Notion工具使用指南，包含常见问题解决方案和最佳实践。使用当： (1) 访问Notion数据库view URL出现"URL type view not currently supported"错误， (2) 需要获取数据库schema和表结构信息， (3) 查询数据库中的条目内容， (4) 创建页面时MULTISELECT字段值不存在导致失败， (5) 需要更新数据库schema添加新选项， (6) 开发需要集成Notion数据的自动化工作流， (7) querydatasources/query-database-view返回Business Plan要求错误， (8) 需要在无Business…
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.