ghostonbutterbread/ryushe-proxy
skills/ryushe-proxy/SKILL.md
Inspect or compare Ryushe's personal Caido traffic from an approved Hoster agent.
data-ai
Updated May 28, 2026
$ install --global
skillsauthnpx skillsauth add ghostonbutterbread/bug-bounty-harness ryushe-proxyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 28, 2026, 2:30 AM130.4s1 file scanned
SKILL.md
- name:
- ryushe-proxy
- description:
- Inspect or compare Ryushe's personal Caido traffic from an approved Hoster agent.
Ryushe Proxy
Use this only when the task explicitly asks to view, inspect, or compare Ryushe's personal Caido traffic.
This is not the default agent proxy. Normal spawned agents should use agent-proxy.
Phrase mapping: "my proxy", "Ryushe's proxy", "my Caido", or "Ryushe's Caido" means this Ryushe lane. "Your proxy", "agent proxy", "Ghost proxy", "OpenClaw proxy", or "local proxy" from the agent's point of view means the agent lane instead; load agent-proxy.
Endpoint
From Hoster only:
http://ryushespc:3333/mcp
If the current agent is not running on Hoster, do not try to reach this endpoint directly. Report that Ryushe-lane proxy access is Hoster-only unless Ryushe approves a tunnel or alternate route.
Current boundary note: the Ghost/OpenClaw host, also referred to as ghostonbread, cannot currently connect to http://ryushespc:3333/mcp. Agents running there must not attempt direct Ryushe-proxy access; they should use agent-proxy for Hoster/agent-lane traffic and ask for a Hoster agent or approved tunnel if Ryushe-lane comparison is needed.
Workflow
- Confirm the task explicitly asks for Ryushe-lane traffic review or comparison.
- Confirm the agent is running on Hoster by
GHOST_AGENT_RUNTIME=hoster, hostname, or a trusted runtime note. - Connect to
http://ryushespc:3333/mcp. - Inspect only the relevant project/history/workflow requested.
- Compare equivalent flows against the agent lane when needed.
Guardrails
- Read/compare by default; do not mutate Ryushe's Caido projects unless requested.
- Do not copy cookies, bearer tokens, API keys, or other secrets from Ryushe's proxy into agent browsers/API clients unless Ryushe explicitly approves that action.
- Do not print, persist, or paste raw secrets from Ryushe's traffic into prompts, chat, logs, findings, reports, commits, or notes.
- Keep Ryushe-lane evidence labeled separately from agent-lane evidence.
Related Skills
ghostonbutterbread/stored-xss
documentation
VerifiedTrustedCommunity
Use when attacker-controlled input is saved and rendered later in a profile, comment, title, notification, admin view, export, email, feed, upload metadata, or other stored render surface.
SKILL.mdUpdated Jun 6, 2026
ghostonbutterbread/reflected-xss
content-media
VerifiedTrustedCommunity
Use when attacker-controlled input appears in the immediate HTTP response or browser-rendered page and needs reflected XSS context classification, payload selection, mutation, and browser verification.
SKILL.mdUpdated Jun 6, 2026
ghostonbutterbread/pwnfox
data-ai
VerifiedTrustedCommunity
Use when inspecting proxy traffic from PwnFox-profiled browser sessions, filtering Caido/Burp/proxy history by X-PwnFox-Color, or interpreting user phrases like 'Red session' as a distinct browser/auth/profile lane.
SKILL.mdUpdated Jun 6, 2026
ghostonbutterbread/skills/lfi
tools
VerifiedTrustedCommunity
# LFI — Local File Inclusion Bypass ## What It Does Tests LFI bypass techniques: path traversal, null bytes, wrappers, log poisoning. Load `general-security-testing-policy`, `live-testing-policy`, and `injection-testing-policy` before live testing. For file/path sinks, absence of an immediate file read or response delta is not a stop reason by itself; use the policy to reason about path normalization, extension allowlists, wrappers, encoding, parser differences, and stack-specific proof ladder
SKILL.mdUpdated Jun 6, 2026