agentpack: Skill for Codex

.agents/skills/analyze-proxy-log/SKILL.md

analyze-proxy-log is a skill for Codex from OlegHQ/agentpack. It costs 81 tokens per session (473 once invoked), scanned A, original, MIT.

A diagnostic procedure for JSONL logs from the agentpack Claude proxy, where JSONL means one JSON record per line. It looks for hangs, connection problems, authentication failures, upstream errors, and stalled requests.

In plain words
What is it for?
Use it to analyze proxy logs, find the affected request and transport, identify the first failing event, and report the exact log path.
Why use it?
It helps identify where a proxy request failed and separates issues in the agent, network connection, authentication, or upstream service.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is OlegHQ/agentpack's own configuration. It tells Codex how to work on agentpack itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentpack configures →

Reuse

Borrowing it

Nothing to install: this file belongs to OlegHQ/agentpack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/OlegHQ/agentpack/dev/.agents/skills/analyze-proxy-log/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/OlegHQ/agentpack

Made for: Codex.

Wrote 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.

agentmods badge for analyze-proxy-log

README.md
[![agentmods](https://agentmods.dev/badge/skills/oleghq/agentpack/analyze-proxy-log/github.svg)](https://agentmods.dev/skills/oleghq/agentpack/analyze-proxy-log)
Your own site
<a href="https://agentmods.dev/skills/oleghq/agentpack/analyze-proxy-log"><img src="https://agentmods.dev/badge/skills/oleghq/agentpack/analyze-proxy-log/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.

agentmods 80×15 button for analyze-proxy-log

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 473 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.00473
Opus 5.5 $0.00032 $0.00189
Sonnet 5.5 $0.00016 $0.00095
Haiku 4.5 $0.00008 $0.00047

Measured 2mo ago against content hash 75ac3b04b897, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/analyze_proxy_log.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/analyze-proxy-log/SKILL.md · 37 lines

What it actually says

Analyze Proxy Log

Use this skill to quickly diagnose agentpack --proxy claude failures from the proxy JSONL log.

Workflow

  1. 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.
  2. Run scripts/analyze_proxy_log.py with the log file or log directory.
  3. Read the summary first, then inspect the request timelines flagged as LIKELY ISSUE.
  4. 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.
  5. 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.

Files

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.

Changes

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.

  1. 2mo ago First seen · 37 lines · 81 tokens per session scan A 75ac3b04b897

Subscribe to this mod's changes

analyze-proxy-log is a skill published in the GitHub repository OlegHQ/agentpack (16 stars, last pushed 22d ago), licensed MIT. It adds 81 tokens to every session and 473 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-08-30.

Related

analyze-proxy-log compared with skills from other repositories

analyze-proxy-log next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
analyze-proxy-logOlegHQ/agentpackSkill1622d agoMITA81Codex
systematic-debuggingdamianvtran/local-operatorSkill229yesterdayMITA45Claude Code, Codex
regexbug-ops/zephSkill663d agoMITA85Claude Code, Codex
code-analysisbug-ops/zephSkill663d agoMITA105Claude Code, Codex
networkbug-ops/zephSkill663d agoMITA83Claude Code, Codex
sephera-change-safetyReim-developer/SepheraSkill777d agoGPL-3.0A80Claude Code, Codex
tracelet-instrumentjnMetaCode/skilletSkill21mo agoMITA51Claude Code, Codex