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/jmstar85/oh-my-githubcopilot/push-omcnpx skills add jmstar85/oh-my-githubcopilot --skill push-omcgit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWrote 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/jmstar85/oh-my-githubcopilot/push-omc)<a href="https://agentmods.dev/skills/jmstar85/oh-my-githubcopilot/push-omc"><img src="https://agentmods.dev/badge/skills/jmstar85/oh-my-githubcopilot/push-omc.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.00000 | $0.01479 |
| Opus 5 | $0.00000 | $0.00740 |
| Sonnet 5 | $0.00000 | $0.00296 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
push-omc 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/push-omc — Export OMG Session into OMC (omg → omc)
Trigger
- Slash command:
/push-omc - Keywords: "push omc", "omc 푸시", "omc로 보내기", "sync to omc", "export to omc"
Purpose
Push the local OMG (oh-my-githubcopilot) session into OMC (oh-my-claudecode) so work done in GitHub Copilot can continue in Claude Code. Counterpart of /resume-claude. Together they form the v1.4.3 bidirectional bridge (OMG ↔ OMC).
Workflow
Step 1 — Detect
Call omg_detect_external_session and find the entry where source === "omg" (the local session). If has_checkpoint is false, abort:
"OMG 체크포인트가 없습니다.
omg_checkpoint를 먼저 호출해 현재 상태를 저장해주세요."
Step 2 — Compare
Call omg_compare_checkpoints. Look at external[].omg_newer_than_external to decide whether the push will progress real work or just collide.
Display:
현재 OMG 체크포인트: {timestamp}
OMC 상태:
- 마지막 OMC 체크포인트: {external[omc].timestamp or "없음"}
- OMG가 더 최신: {omg_newer_than_external ? "예" : "아니요"}
If OMC is newer (!omg_newer_than_external && external[omc].timestamp), warn the user — without force: true, files newer on the OMC side will go to conflicts[].
Step 3 — Confirm
Use vscode_askQuestions to confirm export and gate force carefully:
header: "push-omc"
question: "OMG 세션을 OMC로 푸시하시겠습니까?"
options:
- label: "표준 푸시 (충돌 시 건너뜀)"
description: ".omc/ 파일이 더 최신이면 보존하고 conflicts[]에 보고"
recommended: true
- label: "강제 푸시 (--force, .previous.{ISO}.json 백업 생성)"
description: "OMC 측 변경을 덮어쓰고 회전 백업 3개를 유지"
- label: "취소"
allowFreeformInput: false
Strong-default the standard option. Force mode should be a deliberate user choice — once .previous.{ISO}.json rotation hits N=3, older snapshots are pruned.
Step 4 — Export
Call omg_export_external_session({target: "omc", force: <chosen>}).
Pre-flight:
- The exporter applies a project-identity guard. If the source checkpoint's
workspace_root≠ current workspace, it returns{ success: false, reason: "workspace_mismatch" }BEFORE any file mutation. Surface the error and stop.
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 · 113 lines · 0 tokens per session scan A a0b1cc2671e3
push-omc is a skill published in the GitHub repository jmstar85/oh-my-githubcopilot (153 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,479 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-30.
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…