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/troylar/devsync-mcp/sync-teamnpx skills add troylar/devsync-mcp --skill sync-teamgit clone --depth 1 https://github.com/troylar/devsync-mcpWhat 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.00000 | $0.00822 |
| Opus 5 | $0.00000 | $0.00411 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
sync-team 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync-team — AI-Merge Team Configurations
Sync your team's standard dev configurations with intelligent AI-powered merging. This skill pulls team config profiles and uses your IDE's LLM to intelligently merge them with your existing personal configurations — preserving your customizations while incorporating team standards.
Prerequisites
The devsync-mcp MCP server must be configured. Add to your MCP settings:
{
"mcpServers": {
"devsync-mcp": {
"command": "devsync-mcp",
"transport": "stdio"
}
}
}
Workflow
Step 1: Ask for the team profile
Ask the user for their team config repository URL if not already known:
"What's the Git URL for your team's config profile? (e.g., https://github.com/acme/team-configs)"
Step 2: Pull the team profile
Use the pull_team_profile MCP tool:
pull_team_profile(git_url="<user's URL>")
Report the profile name, version, and number of configs found.
Step 3: Show available configs
Use list_profile_configs with the namespace from step 2:
list_profile_configs(namespace="<namespace>")
Present the list to the user in a readable format:
| Config | Type | Target | Description |
|---|---|---|---|
| ... | ... | ... | ... |
Step 4: Check current status
Use get_merge_status to see what's already been merged:
get_merge_status(namespace="<namespace>")
Show which configs are pending, merged, or changed since last merge.
Step 5: Preview and merge each config
For each config the user wants to merge (or all pending ones):
-
Preview: Call
preview_merge(namespace, config_name)to get both source (team) and target (your current) content. -
Analyze: Read both contents carefully. Understand the semantics:
- For shell profiles: identify aliases, exports, PATH additions, functions
- For git configs: identify sections, settings, aliases
- For AI rules: identify standards, conventions, patterns
- For editor configs: identify formatting rules, settings
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.
- yesterday First seen · 116 lines · 0 tokens per session scan A 76a84b1046d4
sync-team is a skill published in the GitHub repository troylar/devsync-mcp (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 822 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…