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/jmsa/argus/network-debugnpx skills add Jmsa/argus --skill network-debuggit clone --depth 1 https://github.com/Jmsa/argusWhat 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.00036 | $0.00654 |
| Opus 5 | $0.00018 | $0.00327 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
network-debug 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 yesterday.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate network activity on $ARGUMENTS using the Argus MCP tools.
Steps
-
Set up recording
browser_launch tab_open { url: "$ARGUMENTS" } network_start_recording { targetId } console_start { targetId } -
Navigate and exercise the page
tab_navigate { targetId, url: "$ARGUMENTS" } page_evaluate { targetId, expression: "window.scrollTo(0, document.body.scrollHeight)" } -
Inspect all requests
network_get_requests { targetId } -
Filter to find problems
network_get_requests { targetId, hasError: true } ← failed/cancelled network_get_requests { targetId, status: 404 } ← not found network_get_requests { targetId, status: 500 } ← server errors network_get_requests { targetId, url: "/api/orders" } ← specific endpoint network_get_requests { targetId, method: "POST" } ← mutations -
Verify mock interception if needed
network_add_mock { targetId, urlPattern: "https://api.example.com/**", responseCode: 200, responseBody: '{"mocked": true}' } network_list_mocks { targetId } page_reload { targetId } network_get_requests { targetId, url: "api.example.com" } -
Clean up and test real network
network_clear_mocks { targetId } network_clear_requests { targetId } page_reload { targetId } network_get_requests { targetId } -
Report findings — include:
- Failed or errored requests with status codes
- Slow requests (high
durationvalues) - Unexpected response bodies or status codes
- Screenshot of the page state
- Recommended fixes
Request Entry Fields
| Field | Description |
|---|---|
url |
Full request URL |
method |
HTTP method |
status |
HTTP status code |
mimeType |
Response MIME type |
responseBody |
Response body string |
duration |
Request duration in ms |
error |
Error text if request failed |
type |
Resource type (XHR, Fetch, Script, etc.) |
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.
- yesterday First seen · 87 lines · 36 tokens per session scan A a029982ce844
network-debug is a skill published in the GitHub repository Jmsa/argus (0 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 654 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-31.
Other skills, from other repositories
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
pinchtab-stealth-score
Run the PinchTab stealth-score sweep against 15 bot-detection / fingerprint sites (sannysoft, rebrowser, deviceandbrowserinfo, iphey, whoer, browserscan, pixelscan, fingerprint-scan, incolumitas, fvision, amiunique, browserleaks, creepjs, coveryourtracks, fingerprint-demo). Starts a Docker PinchTab container per…
openbot-data-access
Governs how the OpenBot browser app reads and writes server data — every request goes through client in app/src/lib/client.ts, every read is a queryOptions factory in app/src/lib/ /queries.ts, every write is a mutationOptions factory in app/src/lib/ /mutations.ts, and components consume them through…
openbot-screen-layout
The default layout for every OpenBot configuration screen — PageShell and its prose/wide widths, PageSection and PageRows, Item row composition, the settings-row pattern where a summary and a chevron open a dialog, and the size and variant vocabulary. This is what a new screen looks like unless an instruction says…