browser-runtime-tracing

browser-runtime-tracing is a skill for Codex from manyuegong33/r0crawl_skills. It costs 41 tokens per session (438 once invoked), scanned A, original, no licence file.

A reverse-engineering workflow for tracing what happens inside a browser while software runs. Runtime tracing means recording events and behavior during execution rather than only reading files beforehand.

In plain words
What is it for?
Use it to record browser events, correlate runtime behavior with static evidence, choose an analysis method, and produce a repeatable result.
Why use it?
It helps reveal behavior that is hidden, generated at runtime, or dependent on the browser state. The workflow keeps observations and conclusions reproducible.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to record browser events, correlate runtime behavior with static evidence, choose an analysis method, and produce a repeatable result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/manyuegong33/r0crawl_skills/browser-runtime-tracing
Install

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.

Any agent
npx skills add manyuegong33/r0crawl_skills --skill browser-runtime-tracing
Clone the repo
git clone --depth 1 https://github.com/manyuegong33/r0crawl_skills

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 browser-runtime-tracing

README.md
[![agentmods](https://agentmods.dev/badge/skills/manyuegong33/r0crawl_skills/browser-runtime-tracing/github.svg)](https://agentmods.dev/skills/manyuegong33/r0crawl_skills/browser-runtime-tracing)
Your own site
<a href="https://agentmods.dev/skills/manyuegong33/r0crawl_skills/browser-runtime-tracing"><img src="https://agentmods.dev/badge/skills/manyuegong33/r0crawl_skills/browser-runtime-tracing/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 browser-runtime-tracing

Your own site · 80×15
<a href="https://agentmods.dev/skills/manyuegong33/r0crawl_skills/browser-runtime-tracing"><img src="https://agentmods.dev/badge/skills/manyuegong33/r0crawl_skills/browser-runtime-tracing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 438 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.
Origin unknown 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.00041 $0.00438
Opus 5 $0.00020 $0.00219
Sonnet 5 $0.00008 $0.00088
Haiku 4.5 $0.00004 $0.00044

Measured 11d ago against content hash 86ed4bd64af2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

browser-runtime-tracing 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 11d 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.

skills/browser-runtime-tracing/SKILL.md · 42 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Files

What ships with it

1 file 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. 11d ago First seen · 42 lines · 41 tokens per session scan A 86ed4bd64af2

Subscribe to this mod's changes

browser-runtime-tracing is a skill published in the GitHub repository manyuegong33/r0crawl_skills (221 stars, last pushed 1mo ago), with no licence file. It adds 41 tokens to every session and 438 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.

Related

Other skills, from other repositories

chrome-devtools-cli

Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.

ChromeDevTools/chrome-devtools-mcp · 31 tokens

a11y-debugging

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

ChromeDevTools/chrome-devtools-mcp · 50 tokens

chrome-devtools

Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).

ChromeDevTools/chrome-devtools-mcp · 55 tokens

chrome-performance-optimizer

Autonomous multi-agent performance optimization loop for Chromium and V8. Supports profile-seeded mode (analyzing Speedometer 3 / JetStream profiles via pprof or Sagacity MCP) and pattern-driven discovery mode (fan-out exploration of Blink and V8 macro-patterns grounded in historical wins and past rejected CLs).…

chromium/chromium · 119 tokens

nullaway

Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.

chromium/chromium · 43 tokens

bisect

Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.

chromium/chromium · 52 tokens