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/coralogix/cx-cli/create-prnpx skills add coralogix/cx-cli --skill create-prgit clone --depth 1 https://github.com/coralogix/cx-cliWhat 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.00051 | $0.01404 |
| Opus 5 | $0.00026 | $0.00702 |
| Sonnet 5 | $0.00010 | $0.00281 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
create-pr 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 3d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Create a GitHub pull request for the current branch with an auto-generated title and summary.
Prerequisites
Verify gh is installed and authenticated by running gh auth status. If it fails, tell the user to run gh auth login.
Workflow
1. Understand the current state
Run these in parallel:
git status- check for uncommitted changesgit log --oneline -20- recent commit historygit rev-parse --abbrev-ref HEAD- current branch namegit remote show origin | grep 'HEAD branch'- detect the default base branch (usuallymainormaster)
2. Handle uncommitted changes
If there are staged or unstaged changes, ask the user whether they'd like to commit them before creating the PR. Do not commit or push without explicit approval.
3. Handle pushing
Check if the current branch has a remote tracking branch and is up to date:
git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null
If the branch isn't pushed or is ahead of the remote, ask the user before pushing. Push with -u to set up tracking.
4. Analyze changes
Most of the code in this repo is LLM-generated, so reviewers lean on the PR description more than the diff. Your job here is to gather enough material to fill every section of the template in step 5 — not just enumerate what changed.
Look at ALL commits on the branch, not just the latest one:
git log <base-branch>..HEAD # full messages, not just --oneline
git diff <base-branch>...HEAD
git rev-parse --abbrev-ref HEAD # branch name often carries a ticket ID
While reading, deliberately collect:
- Why the change exists (commit messages, branch name, linked tickets)
- How it works at a high level (which modules/layers, data/control flow)
- Non-obvious decisions (anything a reviewer might question)
- Behavioral / interface / schema changes (what's different about the system after merge)
- What was actually tested (look for test files added, but verify with the user / run history)
- Risks (breaking changes, migrations, blast radius)
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.
- 3d ago First seen · 165 lines · 51 tokens per session scan A 684af9ba915f
create-pr is a skill published in the GitHub repository coralogix/cx-cli (115 stars, last pushed 3d ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,404 once invoked, about $0.0003 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-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…