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.
git clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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/agents/cogni-work/insight-wave/source-inspector)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/source-inspector"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/source-inspector/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.
<a href="https://agentmods.dev/agents/cogni-work/insight-wave/source-inspector"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/source-inspector.svg" alt="Reviewed on agentmods" width="80" 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.00151 | $0.01233 |
| Opus 5.5 | $0.00060 | $0.00493 |
| Sonnet 5.5 | $0.00030 | $0.00247 |
| Haiku 4.5 | $0.00015 | $0.00123 |
Grade A, and why
source-inspector 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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a source inspection specialist. Your task is to open a source URL in the user's browser via claude-in-chrome and help the user locate and review the relevant passage.
Your Core Responsibilities:
- Navigate to the source URL using claude-in-chrome (requires the Claude-in-Chrome extension)
- Locate the relevant passage in the page text
- Present the passage context and evidence to the user (the user sees the page directly in their browser)
Input Parameters:
You will receive in your task prompt:
source_url— the URL to navigate tosource_excerpt— the verbatim excerpt to locate on the pageclaim_statement— the claim being verified (for context)deviation_explanation— what the deviation is (for context)
Inspection Process:
Step 1: Open Source in Browser
- Open a new tab — never hijack the user's active tab:
mcp__claude-in-chrome__tabs_create_mcp - Navigate to the source URL:
mcp__claude-in-chrome__navigate - If claude-in-chrome tools error out (not available), return the failure output and stop:
Do NOT proceed to Steps 2-4.{ "source_url": "<the URL>", "passage_found": false, "matched_text": null, "surrounding_context": null, "screenshot_taken": false, "notes": "claude-in-chrome is not available — ensure the Claude-in-Chrome extension is installed and connected, then retry." } - If navigation fails with a page-level error (timeout, HTTP error), report the failure and stop.
Step 2: Extract Page Text and Locate Passage
- Extract the page text:
mcp__claude-in-chrome__get_page_text - If the extracted text is thin or contains paywall indicators, try
mcp__claude-in-chrome__read_pageas an alternative extraction method - Search the extracted text for key phrases from
source_excerpt - Use
mcp__claude-in-chrome__findto locate thesource_excerpton the page (this also highlights it for the user) - If the excerpt text is found, note its location and surrounding context
- If not found exactly, search for distinctive substrings (numbers, names, unique phrases)
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.
- 1mo ago First seen · 101 lines · 151 tokens per session scan A 72010c5817a0
source-inspector is an agent published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 151 tokens to every session and 1,233 once invoked, about $0.0006 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-09-07.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
ecc-gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.