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 eric861129/SKILLS_All-in-one --skill charles-proxy-extractgit clone --depth 1 https://github.com/eric861129/SKILLS_All-in-oneWrote 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/eric861129/skills_all-in-one/charles-proxy-extract)<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/charles-proxy-extract"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/charles-proxy-extract/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/eric861129/skills_all-in-one/charles-proxy-extract"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/charles-proxy-extract.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.00069 | $0.01411 |
| Opus 5.5 | $0.00028 | $0.00564 |
| Sonnet 5.5 | $0.00014 | $0.00282 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
charles-proxy-extract 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 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.
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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Charles Proxy Session Extractor
Parses and extracts structured data from Charles Proxy session files (.chlsj format).
Prerequisites
- Python 3.x (no external dependencies required)
- Charles Proxy session file in .chlsj format
When to Use This Skill
Use this skill when the user:
- Mentions "Charles Proxy" or "Charles session"
- Asks to "extract", "analyze", or "inspect" .chlsj files
- Wants to filter HTTP/HTTPS requests by endpoint or method
- Needs to examine API request/response data from proxy logs
- Wants to export network traffic data to JSON
How to Execute This Skill
When the user asks to extract, analyze, or inspect Charles Proxy session files, run the Python script using the Bash tool:
python3 ./extract_responses.py <file.chlsj> <pattern> [options]
Required Parameters
<file.chlsj>- Path to the Charles Proxy session file (use exact path provided by user)<pattern>- URL path pattern to match (e.g., "/today", "/logs", "/" for all)
Optional Flags
-m, --method METHOD- Filter by HTTP method (GET, POST, PUT, PATCH, DELETE)-f, --first-only- Show only first matching request (for quick inspection)-s, --summary-only- Show statistics without response bodies-o, --output FILE- Save responses to JSON file--no-pretty- Disable JSON pretty-printing
Execution Examples
Extract all /today responses:
python3 ./extract_responses.py session.chlsj "/today"
Filter by POST method (automatically shows request bodies):
python3 ./extract_responses.py session.chlsj "/logs" --method POST
Quick peek (first result only):
python3 ./extract_responses.py session.chlsj "/users" --first-only
Summary without bodies:
python3 ./extract_responses.py session.chlsj "/" --summary-only
Export to file:
python3 ./extract_responses.py session.chlsj "/items" --output items_data.json
User Request Patterns
When users say things like:
- "Extract [endpoint] from [file]" → Use basic extraction with pattern matching
- "Show POST/PUT/PATCH to [endpoint]" → Add
--methodflag (request bodies auto-shown) - "First [endpoint] response" → Add
--first-onlyflag - "Summarize [file]" or "What's in [file]" → Add
--summary-onlyflag - "Save [endpoint] to [output]" → Add
--outputflag - "Compare [endpoint] with model" → Extract first response, then analyze structure
What ships with it
3 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 · 181 lines · 69 tokens per session scan A 250a6ea722ad
charles-proxy-extract is a skill published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 6mo ago), licensed MIT. It adds 69 tokens to every session and 1,411 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
ck:fix
Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts --from-quality or --from-test to fix exactly the findings/failures a report lists.…
When Stuck - Problem-Solving Dispatch
Dispatch to the right problem-solving technique based on how you're stuck.
thinking-map-territory
When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
pair-programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
debugging
Systematic root-cause debugging with verification. Use for errors, stack traces, broken tests, flaky tests, regressions, or anything not working as expected. For validating bug reports before fixing, use bug-reproduction-validator agent.