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 AFK-surf/OpenBridge --skill bridge-agent-log-analyzergit clone --depth 1 https://github.com/AFK-surf/OpenBridgeWrote 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/afk-surf/openbridge/bridge-agent-log-analyzer)<a href="https://agentmods.dev/skills/afk-surf/openbridge/bridge-agent-log-analyzer"><img src="https://agentmods.dev/badge/skills/afk-surf/openbridge/bridge-agent-log-analyzer.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.1 | $0.00041 | $0.01109 |
| Opus 5 | $0.00020 | $0.00554 |
| Sonnet 5 | $0.00008 | $0.00222 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
bridge-agent-log-analyzer 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 7d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bridge Agent Log Analyzer
Overview
Inspect one persisted Bridge session and turn its on-disk logs into a behavior report.
This skill is for analyzing the agent itself:
- what it tried to do
- which tools it called
- which calls ran in the background
- where it failed
- how it recovered or retried
- which artifacts it read or produced
This skill is not for UI reconstruction. Ignore frontend display behavior unless the user explicitly asks for it.
Default Workflow
- Identify the target session or log identifier.
- Run
scripts/inspect_bridge_session.pyfirst. - Read only the raw files needed to explain the behavior:
session-meta.jsonagent/history.jsonagent/context.jsonagent/state.jsonagent/toolcalls/*/meta.jsonagent/toolcalls/*/output.log- subagent equivalents under
agents/<subagent-id>/agent/
- Reconstruct the execution chronologically.
- Separate direct evidence from inference.
Quick Start
Inspect the most recent session:
python3 .agents/skills/bridge-agent-log-analyzer/scripts/inspect_bridge_session.py
Inspect a specific session directory ID:
python3 .agents/skills/bridge-agent-log-analyzer/scripts/inspect_bridge_session.py --session-id <session-id>
Inspect using any UUID or identifier that appears inside that session's logs:
python3 .agents/skills/bridge-agent-log-analyzer/scripts/inspect_bridge_session.py --session-id <message-or-toolcall-id>
The helper script is the index. Use it to find the real session directory, runtime toolcalls, failures, and likely recovery paths before opening raw files.
Primary Evidence Sources
history.json- user-visible messages and task state transitions
context.json- assistant decision points, tool calls, and tool results
toolcalls/*/meta.json- runtime command, async promotion, exit code, timing, environment
toolcalls/*/output.log- actual command output, error text, tracebacks, downloads, progress
state.json- model, reasoning effort, last-round token and step summary
session-meta.json- session title, environments, created/updated timestamps
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.
- 7d ago First seen · 180 lines · 41 tokens per session scan A d3c9bba0a706
bridge-agent-log-analyzer is a skill published in the GitHub repository AFK-surf/OpenBridge (426 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,109 once invoked, about $0.0002 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.