Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ShulkwiSEC/bb-hugenpx agentmods add skills/shulkwisec/bb-huge/kaido-proxy-integrationWrote 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/shulkwisec/bb-huge/kaido-proxy-integration)<a href="https://agentmods.dev/skills/shulkwisec/bb-huge/kaido-proxy-integration"><img src="https://agentmods.dev/badge/skills/shulkwisec/bb-huge/kaido-proxy-integration.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.00042 | $0.01580 |
| Opus 5 | $0.00021 | $0.00790 |
| Sonnet 5 | $0.00008 | $0.00316 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
kaido-proxy-integration scanned grade A with 2 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
tools: [kaido, caido, claude-code-cli, typescript, curl] Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const { execSync } = await import("child_process"); Copies of this mod
1 near-identical copy found in the catalogue:
- kaido-proxy-integration — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kaido (Caido) Proxy Integration Skill
When to Use
- When Claude needs to intercept and analyze HTTP traffic through Kaido proxy.
- When automating request modification and replay attacks against target endpoints.
- When Burp Suite is unavailable and Kaido is the primary interception proxy.
Prerequisites
- Kaido (Caido) running on
http://127.0.0.1:8080 - Kaido API enabled (GraphQL endpoint)
- Claude Code CLI installed
- Target within authorized scope
Core Concept
"Build a skill that tells Claude how to interact with Kaido — intercepting, replaying, modifying requests." — Episode 166 [13:46]
Workflow
Phase 1: Query Intercepted Traffic (3-Tier Fallback)
// scripts/intercept.ts — Query Kaido's captured HTTP traffic
const KAIDO_API = process.env.KAIDO_API_URL || "http://127.0.0.1:8080/graphql";
// Tier 1: GraphQL API (preferred)
async function queryTraffic(host?: string) {
try {
const res = await fetch(KAIDO_API, {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
query: `query { requests(filter: "${host ? `host:${host}` : ""}", first: 100) {
edges { node { id method url path responseStatusCode responseLength } }
}}`,
}),
});
if (!res.ok) throw new Error(`API: ${res.status}`);
return (await res.json()).data.requests.edges.map((e: any) => e.node);
} catch {
console.warn("[FALLBACK] GraphQL failed, trying REST...");
return queryTrafficREST(host);
}
}
// Tier 2: REST fallback
async function queryTrafficREST(host?: string) {
try {
const res = await fetch(`http://127.0.0.1:8080/api/requests?limit=100`);
if (!res.ok) throw new Error(`REST: ${res.status}`);
return (await res.json()).filter((r: any) => !host || r.host.includes(host));
} catch {
console.warn("[FALLBACK] REST failed, using curl...");
return queryViaCurl(host);
}
}
// Tier 3: curl fallback
async function queryViaCurl(host?: string) {
const { execSync } = await import("child_process");
const output = execSync(
`curl -s http://127.0.0.1:8080/api/requests 2>/dev/null || echo "[]"`
).toString();
return JSON.parse(output);
}
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.
- 4d ago First seen · 169 lines · 42 tokens per session scan A 7862724f3f72
kaido-proxy-integration is a skill published in the GitHub repository ShulkwiSEC/bb-huge (22 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,580 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
kaido-proxy-integration
Integrate Kaido (Caido) proxy with Claude Code CLI for automated HTTP interception, request replay, and vulnerability scanning. Based on Critical Thinking Ep. 166.
playwright-uitest
Generate Playwright UI tests and visual smoke reports for delivery POC frontends.
aluvia
Use Aluvia when a cloud agent is in the wrong country for a site; when a page says not available in your region, this content is not available in your country, we don’t ship to your location, or other geo-restriction; when you need the browser to use an IP in a specific country (aluvia proxy-on --geo US; run aluvia…
caido-mode
Full Caido SDK integration for Claude Code. Search HTTP history with HTTPQL, test with curl proxied through Caido (caching auth in reusable static curl config files), add match & replace rules, and organize handoffs into named replay sessions and collections - all via the official @caido/sdk-client. PAT auth…
browser-stealth
Browser automation stealth and residential proxy routing — patchright anti-detection, Playwright proxy at correct context level, sticky residential sessions, navigator.webdriver masking, datacenter vs residential IP fingerprinting, and page.evaluate fetch fallback.
browser-test
Browser testing using Chrome DevTools MCP and Playwright for visual verification. Start dev server, navigate, screenshot, Lighthouse audit, console errors, network check. Use when: (1) verifying frontend changes, (2) accessibility auditing, (3) performance testing, (4) visual regression. Triggers: /browser-test, 'test…