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/statusnpx skills add jmstar85/oh-my-githubcopilot --skill statusgit 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/status)<a href="https://agentmods.dev/skills/jmstar85/oh-my-githubcopilot/status"><img src="https://agentmods.dev/badge/skills/jmstar85/oh-my-githubcopilot/status.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.00037 | $0.00481 |
| Opus 5 | $0.00018 | $0.00241 |
| Sonnet 5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
status 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.
This is a copy
97% identical to status — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Status
Show the current state of all OMG modes, active agents, and progress.
When to Use
- Check what mode is currently active
- See progress of omg-autopilot, ralph, or team execution
- Verify state after a cancel or resume
Workflow
1. Scan State Files
Read .omg/state/ directory for active mode state files:
omg-autopilot-state.jsonralph-state.jsonultrawork-state.jsonultraqa-state.jsonteam-state.jsonself-improve/state/agent-settings.json
2. Report Active Modes
For each active mode, show:
OMG Autopilot:
- Current phase (0-5)
- Phase name and progress
- Files modified so far
Ralph:
- Current story (N of M)
- Stories passing / total
- Linked ultrawork status
Team:
- Team name and member count
- Current pipeline stage
- Task completion (N/M tasks done)
UltraQA:
- Current cycle (N of 5)
- Last failure summary
Self-Improve:
- Current iteration
- Best score vs baseline
- Improvement percentage
- Stop condition proximity
3. Report No Active Modes
If nothing is active: "No active OMG modes. Start with /omg-autopilot, /ralph, or /team."
Output Format
=== OMG Status ===
Mode: OMG Autopilot
Phase: 2/5 (Execution)
Started: 2 minutes ago
Files modified: 12
Mode: Team (linked)
Team: fix-ts-errors
Stage: team-exec
Workers: 3/3 active
Tasks: 2/5 completed
Verbose Mode (--verbose)
With --verbose, also show:
- Full state JSON for each active mode
- Recent git log (last 5 commits)
.omg/directory listing
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 · 85 lines · 37 tokens per session scan A c63ad13ebfad
status is a skill published in the GitHub repository jmstar85/oh-my-githubcopilot (153 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 481 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to status, differing in 4 lines, and is treated as a copy.
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…