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 skills add starbaser/ccproxy --skill using-ccproxy-inspectorgit clone --depth 1 https://github.com/starbaser/ccproxyWrote 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/starbaser/ccproxy/using-ccproxy-inspector)<a href="https://agentmods.dev/skills/starbaser/ccproxy/using-ccproxy-inspector"><img src="https://agentmods.dev/badge/skills/starbaser/ccproxy/using-ccproxy-inspector/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/starbaser/ccproxy/using-ccproxy-inspector"><img src="https://agentmods.dev/badge/skills/starbaser/ccproxy/using-ccproxy-inspector.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00130 | $0.02495 |
| Opus 5.5 | $0.00052 | $0.00998 |
| Sonnet 5.5 | $0.00026 | $0.00499 |
| Haiku 4.5 | $0.00013 | $0.00249 |
Grade A, and why
using-ccproxy-inspector scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
optional curl-cffi sidecar for configured fingerprint profiles The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 316 lines · 130 tokens per session scan A 807006fd6c0d
using-ccproxy-inspector is a skill published in the GitHub repository starbaser/ccproxy (355 stars, last pushed 2mo ago), with no licence file. It adds 130 tokens to every session and 2,495 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-workflow
Run the Maestro debugging workflow for investigation-heavy tasks.
perf-check
Run a Maestro-style performance assessment for hotspots, regressions, and optimization planning.
debug-assistant
Systematic debugging assistant that helps identify and fix bugs through structured analysis, hypothesis testing, and root cause identification. Use when facing errors, unexpected behavior, or mysterious bugs.
quick-fix
Apply a minimal, targeted fix to a specific bug or issue. Focused on speed and precision - locate the problem, make the smallest correct change, and verify. Not a planning workflow; use for small fixes, patches, and hotfixes.
troubleshooter
Specialized in system-wide troubleshooting using metrics and logs.
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.