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 Crawlio-app/crawlio-browser --skill dossiergit clone --depth 1 https://github.com/Crawlio-app/crawlio-browserWrote 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/crawlio-app/crawlio-browser/dossier)<a href="https://agentmods.dev/skills/crawlio-app/crawlio-browser/dossier"><img src="https://agentmods.dev/badge/skills/crawlio-app/crawlio-browser/dossier/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/skills/crawlio-app/crawlio-browser/dossier"><img src="https://agentmods.dev/badge/skills/crawlio-app/crawlio-browser/dossier.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.00019 | $0.00868 |
| Opus 5.5 | $0.00008 | $0.00347 |
| Sonnet 5.5 | $0.00004 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
dossier 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dossier — Competitive Intelligence
Compare a target site against 2-4 competitors across all 11 comparison dimensions. Aggregate strengths, weaknesses, and opportunities as structured findings.
When to Use
- Building a competitive analysis across multiple sites
- Comparing tech stacks, performance, accessibility, SEO head-to-head
- Identifying where a target leads or lags vs competitors
- Producing a structured strengths/weaknesses/opportunities report
Protocol
- search for comparison commands:
search("compare pages")orsearch("extract page") - connect_tab to the target URL with
{ background: true } - execute Code Mode to run
smart.comparePages()for each target-vs-competitor pair - Emit one
smart.finding()per dimension per pair - After all pairs, return
smart.findings()grouped by dimension
Code Example
const target = "https://target.com";
const competitors = ["https://comp-a.com", "https://comp-b.com"];
// Compare target vs each competitor
for (const comp of competitors) {
const comparison = await smart.comparePages(target, comp);
for (const dim of comparison.scaffold.dimensions) {
if (!dim.comparable) continue;
smart.finding({
claim: `${dim.name}: ${target} vs ${comp}`,
evidence: [
`target (${dim.siteA.type}): ${JSON.stringify(dim.siteA.value)}`,
`competitor (${dim.siteB.type}): ${JSON.stringify(dim.siteB.value)}`
],
sourceUrl: target,
confidence: "high",
method: "comparePages",
dimension: dim.name
});
}
// comparePages returns PageEvidence, not technographic results. Detect each stack explicitly.
const compTech = (await smart.detectTechnologies()).technologies.map(t => t.name);
await smart.navigate(target);
const targetTech = (await smart.detectTechnologies()).technologies.map(t => t.name);
if (targetTech.length || compTech.length) {
smart.finding({
claim: `Tech stacks differ: target [${targetTech.join(", ")}] vs ${comp} [${compTech.join(", ")}]`,
evidence: [`target: ${targetTech.join(", ")}`, `competitor: ${compTech.join(", ")}`],
sourceUrl: target,
confidence: "high",
method: "detectTechnologies",
dimension: "framework"
});
}
}
// Visual reference of target
await smart.scrollCapture();
return { findings: smart.findings(), totalComparisons: competitors.length };
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 · 97 lines · 19 tokens per session scan A 0dbbfe55f624
dossier is a skill published in the GitHub repository Crawlio-app/crawlio-browser (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 868 once invoked, about $0.0001 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-31.
Other skills, from other repositories
owb
Open Web Bridge (OWB) — drive the user's own real browser with the owb command. Read pages behind their existing logins, gather and cross-check information, fill forms, walk multi-step flows, debug their site, audit responsive/accessibility behavior, and capture or reverse-engineer network traffic. Use this whenever…
katashiro-guided-runbook
Guide a human operator through a multi-step operation (production change, migration, backfill, load or outage test, incident fix) as a live runbook canvas in Katashiro — the human runs every command; you write the runbook, point at the next step, check each pasted output against what was expected, and keep the…
katashiro-point-at
Point the user at something in the browser while you explain it — glow an element on the page they are looking at (katashiro.highlight), emphasise several parts at once with temporary CSS (katashiro.injectcss), glow a block in a Katashiro canvas (katashiro.canvashighlight), or emphasise several parts of a canvas with…
katashiro-ask-user
Ask the user a multiple-choice question as a clickable card in their Katashiro side panel (katashiro.askuser), then end your turn — the answer arrives later as a new message. Use when you are chatting through Katashiro and need the user to pick between a few clear alternatives (which file, which approach, which of…
katashiro-show-image
Show an image to the user in their Katashiro side panel (a chart, diagram, rendered output, or a screenshot you took) without passing the image bytes through the model. Use when you are chatting with the user through Katashiro and a picture would explain better than text. Keywords — show image, send image, display…
browser
Use this skill when the user says browser, /browser, test in Chrome, inspect a webpage, verify a localhost app, capture screenshots, check console/network errors, run browser QA, or automate browser flows with the Mochi browser MCP.