LLM Models
majiayu000/claude-skill-registry
Access Claude, Gemini, Kimi, GLM and 100+ LLMs via inference.sh CLI using OpenRouter.
Operates the ccproxy inspector MITM system for intercepting, inspecting, and transforming LLM API traffic.
Install Using Ccproxy Inspector
$ npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install starbaser/ccproxy using-ccproxy-inspector --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/starbaser/ccproxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/using-ccproxy-inspector .claude/skills/using-ccproxy-inspector && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "using-ccproxy-inspector" agent skill from https://github.com/starbaser/ccproxy/tree/dev/skills/using-ccproxy-inspector into .claude/skills/using-ccproxy-inspector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ccproxy-inspector", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/starbaser/ccproxy/tree/dev/skills/using-ccproxy-inspectorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install starbaser/ccproxy using-ccproxy-inspector --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/starbaser/ccproxy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/using-ccproxy-inspector .agents/skills/using-ccproxy-inspector && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "using-ccproxy-inspector" agent skill from https://github.com/starbaser/ccproxy/tree/dev/skills/using-ccproxy-inspector into .agents/skills/using-ccproxy-inspector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ccproxy-inspector", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install starbaser/ccproxy using-ccproxy-inspector --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/starbaser/ccproxy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/using-ccproxy-inspector .cursor/skills/using-ccproxy-inspector && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "using-ccproxy-inspector" agent skill from https://github.com/starbaser/ccproxy/tree/dev/skills/using-ccproxy-inspector into .cursor/skills/using-ccproxy-inspector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ccproxy-inspector", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/starbaser/ccproxy.git --path skills/using-ccproxy-inspector--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install starbaser/ccproxy using-ccproxy-inspector --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/starbaser/ccproxy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/using-ccproxy-inspector .gemini/skills/using-ccproxy-inspector && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "using-ccproxy-inspector" agent skill from https://github.com/starbaser/ccproxy/tree/dev/skills/using-ccproxy-inspector into .gemini/skills/using-ccproxy-inspector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ccproxy-inspector", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install starbaser/ccproxy using-ccproxy-inspectorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/starbaser/ccproxy.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/using-ccproxy-inspector .github/skills/using-ccproxy-inspector && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "using-ccproxy-inspector" agent skill from https://github.com/starbaser/ccproxy/tree/dev/skills/using-ccproxy-inspector into .github/skills/using-ccproxy-inspector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ccproxy-inspector", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install starbaser/ccproxy using-ccproxy-inspector --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/starbaser/ccproxy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/using-ccproxy-inspector .opencode/skills/using-ccproxy-inspector && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "using-ccproxy-inspector" agent skill from https://github.com/starbaser/ccproxy/tree/dev/skills/using-ccproxy-inspector into .opencode/skills/using-ccproxy-inspector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-ccproxy-inspector", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
using-ccproxy-inspector- GitHub stars
- 350
- Token cost
- ~2.7k tokens
- SKILL.md length
- 758 words
- Files
- 5 (incl. scripts)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Operates the ccproxy inspector MITM system for intercepting, inspecting, and transforming LLM API traffic.
- Running CLI applications through ccproxy
- SKILL.md covers Inspect First, Running Tools Through ccproxy, Choosing A Capture Mode and Understanding Flow State, plus 5 more sections
- Runs Python scripts from its folder; calls uv
- Inspecting intercepted flows
What it does
Using Ccproxy Inspector is an agent skill from starbaser/ccproxy. Operates the ccproxy inspector MITM system for intercepting, inspecting, and transforming LLM API traffic. Covers running CLI tools through the reverse proxy or permissive WireGuard namespace capture path, checking namespace status and doctor output, inspecting flows with client-vs-forwarded request comparison, understanding the inbound/transform/outbound pipeline, capturing and auditing shape artifacts, applying the privacy guide, and diagnosing flow issues. Use when running CLI applications through ccproxy…
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `reference/flow-api-reference.md`, `scripts/inspect_flow.py` and `scripts/list_flows.py`).
It sits in AI & LLM Engineering, covering LLM API integration, Model routing and gateways and Cloud networking. It works with OpenAI, Anthropic API, Google Gemini and OpenRouter. The repository describes itself as: Build mods for Claude Code: Hook any request, modify any response, /model "with-your-custom-model", intelligent model routing using your logic or ours.
When your agent uses it
- Running CLI applications through ccproxy
- Inspecting intercepted flows
- Comparing client request vs forwarded request
- Checking shaping profile status
Example prompts
- “Use the using-ccproxy-inspector skill to operate the ccproxy inspector MITM system for intercepting, inspecting, and transforming LLM API traffic”
- “/using-ccproxy-inspector”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit f2c4769. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Using Ccproxy Inspector loads about 2.7k tokens when it runs. Until then it costs about 186 tokens; SKILL.md has 758 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 758 words (~2,709 tokens).
“The inspector intercepts LLM API traffic through mitmproxy and routes accepted flows through the ccproxy addon chain:”
- name
- using-ccproxy-inspector
Files
SKILL.md and 4 other files (scripts) in skills/using-ccproxy-inspector of starbaser/ccproxy.
- SKILL.md
- reference/flow-api-reference.md
- scripts/inspect_flow.py
- scripts/list_flows.py
- scripts/shaping_status.py
Open the folder on GitHubat commit f2c4769
Compare with similar skills
Using Ccproxy Inspector next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Using Ccproxy Inspector this skillstarbaser/ccproxy | 350 | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| LLM Modelsmajiayu000/claude-skill-registry | 666 | 1 repos | ~992 | Automated safety check: Pass | MIT | |
| Neon AI Gatewayneondatabase/agent-skills | 100 | — | ~5.1k | Automated safety check: Notes | Apache-2.0 | |
| ModLens Image Vision Bridgeliustack/modlens | 4.2k | 1 repos | ~1.3k | Automated safety check: Notes | MIT | |
| Agent Squad Python Guide2FastLabs/agent-squad | 7.8k | — | ~4.7k | Automated safety check: Pass | Apache-2.0 | |
| Embeddings via 9Routerdecolua/9router | 30k | — | ~604 | Automated safety check: Pass | MIT |
Similar skills
- Official
Neon AI Gateway
neondatabase/agent-skills
One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks.
ModLens Image Vision Bridge
liustack/modlens
Gives text-only models sight by running the modlens CLI on an image path or URL and returning structured JSON evidence with transcribed text, layout and semantics.
Agent Squad Python Guide
2FastLabs/agent-squad
Map of the agent-squad Python framework for async multi-agent orchestration: which agent, classifier, storage and tool provider to pick, and the pitfalls to avoid.
Embeddings via 9Router
decolua/9router
Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.
Provider Integration
hex/claude-council
Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface.
More from starbaser/ccproxy
Using Ccproxy API
starbaser/ccproxy
Guides users through ccproxy as an OpenAI-compatible and Anthropic-compatible LLM API server with SDK integration, OAuth authentication, sentinel key substitution, model routing, and troubleshooting.
Related
Categories
Questions about Using Ccproxy Inspector
What does Using Ccproxy Inspector do?
Operates the ccproxy inspector MITM system for intercepting, inspecting, and transforming LLM API traffic. Using Ccproxy Inspector is an agent skill from starbaser/ccproxy. Operates the ccproxy inspector MITM system for intercepting, inspecting, and transforming LLM API traffic.
When should I use Using Ccproxy Inspector?
Using Ccproxy Inspector fits situations like: running CLI applications through ccproxy; inspecting intercepted flows; comparing client request vs forwarded request; checking shaping profile status.
How do I install Using Ccproxy Inspector in Claude Code?
Run `npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a claude-code`. Or copy the skill folder (skills/using-ccproxy-inspector in starbaser/ccproxy) into .claude/skills/using-ccproxy-inspector in your project. Claude Code loads it when a task matches its description.
How do I install Using Ccproxy Inspector in Codex?
Run `npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a codex`. Or copy the skill folder (skills/using-ccproxy-inspector in starbaser/ccproxy) into .agents/skills/using-ccproxy-inspector in your project. Codex loads it when a task matches its description.
Can I use Using Ccproxy Inspector in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add starbaser/ccproxy --skill using-ccproxy-inspector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-ccproxy-inspector, .gemini/skills/using-ccproxy-inspector, .github/skills/using-ccproxy-inspector and .opencode/skills/using-ccproxy-inspector in your project.
What does Using Ccproxy Inspector need to run?
Going by SKILL.md and its folder, Using Ccproxy Inspector needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.
Does Using Ccproxy Inspector access the network?
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Using Ccproxy Inspector safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Using Ccproxy Inspector use?
Using Ccproxy Inspector has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Using Ccproxy Inspector use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Using Ccproxy Inspector?
Skills that share tags, products or a category with Using Ccproxy Inspector: LLM Models (majiayu000/claude-skill-registry, 666 stars), Neon AI Gateway (neondatabase/agent-skills, 100 stars), ModLens Image Vision Bridge (liustack/modlens, 4.2k stars) and Agent Squad Python Guide (2FastLabs/agent-squad, 7.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Using Ccproxy Inspector?
starbaser (a GitHub user) maintains it in starbaser/ccproxy, which has 350 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 10, 2026.
Source: starbaser/ccproxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.