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/oleghq/agentpack/analyze-proxy-lognpx skills add OlegHQ/agentpack --skill analyze-proxy-loggit clone --depth 1 https://github.com/OlegHQ/agentpackWrote 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/oleghq/agentpack/analyze-proxy-log)<a href="https://agentmods.dev/skills/oleghq/agentpack/analyze-proxy-log"><img src="https://agentmods.dev/badge/skills/oleghq/agentpack/analyze-proxy-log.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.00081 | $0.00473 |
| Opus 5 | $0.00041 | $0.00236 |
| Sonnet 5 | $0.00016 | $0.00095 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
analyze-proxy-log 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.
What it actually says
Analyze Proxy Log
Use this skill to quickly diagnose agentpack --proxy claude failures from the proxy JSONL log.
Workflow
- Locate the log:
- Prefer an explicit path from the user.
- Else read
AGENTPACK_PROXY_LOG_DIR. - Else find the nearest agentpack project root and use
$AGENTPACK_HOME/projects/<project-hash>/proxy-logs/latest.json.
- Run
scripts/analyze_proxy_log.pywith the log file or log directory. - Read the summary first, then inspect the request timelines flagged as
LIKELY ISSUE. - Classify the primary failure:
stalled_request: request accepted but no terminal event.websocket_timeout: connect/read/write timeout or closed-before-terminal WebSocket.websocket_setup: 401/403/429 or setup frame error before a normal response.auth_refresh: refresh attempted and failed or repeated authorization failure.upstream_http: non-success HTTP status from Codex.translation: request or response conversion failed.downstream: Claude disconnected or response write failed.
- Report the likely root cause, the request ID, transport, model mapping, first failing event, and the exact log path.
Commands
python3 .agents/skills/analyze-proxy-log/scripts/analyze_proxy_log.py
python3 .agents/skills/analyze-proxy-log/scripts/analyze_proxy_log.py "$AGENTPACK_PROXY_LOG_DIR"
python3 .agents/skills/analyze-proxy-log/scripts/analyze_proxy_log.py /path/to/proxy-*.jsonl
Do not paste full payload snippets into the final answer unless the user explicitly asks. Logs are sanitized by default, but payload logging may be enabled with AGENTPACK_PROXY_LOG_PAYLOADS=1.
What ships with it
2 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.
- 4d ago First seen · 37 lines · 81 tokens per session scan A 75ac3b04b897
analyze-proxy-log is a skill published in the GitHub repository OlegHQ/agentpack (14 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 473 once invoked, about $0.0004 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
background-watch-hook
Use vibe watch to run a managed Harness waiter that returns to the same conversation later. Best for reviews, CI, files, logs, and other wait-now-continue-later workflows.
check-model
Check model compatibility with xinfer before loading. Validates config.json, weight tensor shapes and naming, quantization format correctness, and multi-rank (tensor-parallel) divisibility. Use when the user asks to check, validate, audit, or verify a model will load correctly — from a HuggingFace URL/config, local…
test-model
Test LLM models served by xinfer for correctness, output quality, and performance. Use when the user asks to test, benchmark, validate, or verify models — either from a local folder path or HuggingFace model IDs. Supports all xinfer-compatible formats: BF16, FP8, MXFP4, NVFP4, GGUF, GPTQ, AWQ, ISQ, Dense, MoE, and…
pr-delivery-loop
The implementation-lane standard for delivering a PR across the Avibe repositories (avibe, avibe-backend, avibe-docs, avault, and vault-sandbox) — branch/scope rules, contracts, Codex-bot review-loop discipline, and close-out criteria. Use this skill for every implementation task in these repos, regardless of agent…
add-model
Adapt and port new LLM model architectures to this xinfer project. Use when the user asks to add, port, support, or adapt a new model (e.g. Llama, Gemma, Qwen, GPT-OSS, DeepSeek, or any HuggingFace architecture) including safetensors and GGUF formats, Dense and MoE architectures, and quantization formats (MXFP4…
rust-agent-handoff
Handoff protocol for the Rust multi-agent development team (rust-architect, rust-developer, rust-testing-engineer, rust-performance-engineer, rust-security-maintenance, rust-code-reviewer, rust-cicd-devops, rust-debugger, rust-critic). Use only when orchestrating subagents via structured YAML files in .local/handoff/.…