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/dyzsasd/dev-loop/sync-reponpx skills add dyzsasd/dev-loop --skill sync-repogit clone --depth 1 https://github.com/dyzsasd/dev-loopWhat 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.00119 | $0.00765 |
| Opus 5 | $0.00060 | $0.00382 |
| Sonnet 5 | $0.00024 | $0.00153 |
| Haiku 4.5 | $0.00012 | $0.00076 |
Grade A, and why
sync-repo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sync-repo — reconcile a repo's registry entry with reality
ROLE: You are the operator-present setup skill that re-detects a registered repo's reality and repairs its registry entry, clone, and worktrees.
MISSION
Ensure the clone exists, diff detected build/merge-check/deploy/remote reality against the registry entry (§19), apply only operator-confirmed changes, and repair the worktree/index state.
BOOT
Operator-present, but each invocation is fresh (§0); boot per §0a (the Topology block + the sections cited below). Inputs:
- The workspace + the registered repo ref (resolve the workspace from cwd); read
repos.<ref>fromdev-loop.json. Sections: §0 §0a §2 §12c §19 §27
JOBS
1. ENSURE the clone
- If
repos.<ref>.pathis missing on disk andrepos.<ref>.remoteis set →git clone <remote> <workspace>/<path>. If no remote is recorded, ask the operator for one (and record it).
2. RE-DETECT (compare to the registry; report drift)
- build/typecheck: re-read
package.jsonscripts / tsconfig; diff againstrepos.<ref>.build. - merge checks: re-parse
.github/workflows/*for the current PRpull_requestjobname:s; diff againstrepos.<ref>.mergeChecks(added/removed checks are the usual reason autoMerge stalls, §12c). - deploy: re-check the release workflow / deploy prefixes vs
repos.<ref>.deploy. - remote:
git -C <path> remote get-url originvsrepos.<ref>.remote.
3. APPLY (only confirmed changes; never silently overwrite hand edits)
Present the diff; for each accepted change, edit repos.<ref> (via
dev-loop team add-repo <ref> --project <owner> … for the flag-covered fields, or a direct
validated edit) and re-run dev-loop doctor. Respect the team deployPolicy ceiling (E06)
— the validated write enforces it.
4. REPAIR
Run dev-loop team repair — it does git worktree repair + prune (fixes absolute-path
breakage after a machine move, §27; see docs/PORTABILITY.md), re-registers the workspace
index, and (service) truncates the hub WAL.
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 · 70 lines · 119 tokens per session scan A fc6140117626
sync-repo is a skill published in the GitHub repository dyzsasd/dev-loop (5 stars, last pushed 5d ago), licensed MIT. It adds 119 tokens to every session and 765 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…