hindwatch@r1
CAUTION· install onlyPublisher claims: "Enables coding agents to read a unified, redacted timeline of Metro JS logs, Android logcat, iOS simulator, and iPhone logs, query incidents and patterns, mark and wait for events, and verify fixes over MCP." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
SECRET_KEY_WORDSConfiguration, not credentials: ADB_SERVER_SOCKET, ANDROID_ADB_SERVER_PORT, ANDROID_HOME, ANDROID_SDK_ROOT, HINDWATCH_CLIENT, HINDWATCH_RUNTIME_DIR, ITERM_SESSION_ID, PERF_ANDROID_PACKAGE, PERF_SECONDS, REAL_PATH, SMOKE_ANDROID_PACKAGE, SMOKE_IOS_BUNDLE, SMOKE_METRO_PORT, SMOKE_SECONDS, TERM_SESSION_ID, WT_SESSION- Where it talks to
- no vendor host named in the codeAlso apple.com, githubusercontent.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names apple.com, githubusercontent.com as well as its own vendor. The guard injects SECRET_KEY_WORDS only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is hindwatch@r1 safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 73/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Collapsed <details> block carrying instructions; Collapsed <details> block carrying instructions; Collapsed <details> block carrying instructions. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
<summary><strong>Codex</strong></summary> Run this in the project folder. This follows the Codex docs but has not yet been tried in a live Codex launch: ```sh cFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><strong>Redaction</strong></summary> Redaction is always on and no config or plugin can turn it off. Every event is redacted before it reaches the buffFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><strong>Claude Code</strong></summary> Put this in `.mcp.json` in the project folder: ```json { "mcpServers": { "hindwatch": { "command": "npx", "args"Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.fix: "install Xcode, then sudo xcode-select -s /Applications/Xcode.app",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.fix: "for iPhone crash reports, install Xcode 15 or newer, then sudo xcode-select -s /Applications/Xcode.app",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// The hand-off file goes only once the children are gone; a kill -9 before that leaves it to sweep.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell." Codex codex mcp add hindwatch -- npx -y hindwatch mcp",Fix: Pin versions and sources; vendor anything fetched at install time.* has exited. A kill -9 at any point leaves the ledger or the hand-off file for the next sweep.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.- `npm run perf`: the CPU, memory, kill -9 and stop budgets on a replay, also wrapped in the leftover check.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return fail(errorMessage(error), `chmod 700 ${dir}, or remove it and let hindwatch recreate it`);Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.throw new DeviceError(`usbmuxd is not running: nothing listens on ${socketPath}`, "restart it with sudo launchctl kickstart -k system/com.apple.usbmuxd");Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.<summary><strong>Project root and daemon lifecycle</strong></summary> The project root is the nearest folder with `hindwatch.config.json` or `package.json`. PasFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct." Claude Code claude mcp add hindwatch -- npx -y hindwatch mcp",Fix: Pin versions and sources; vendor anything fetched at install time.// (kill -9 reclaim), and the loser can grab the lock when the winner drains on stop.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.expect("--help has the MCP setup", help.stdout.includes("npx -y hindwatch mcp"));Fix: Pin versions and sources; vendor anything fetched at install time.'wait $c; s=$?; kill $w 2>/dev/null; exit $s';Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* child and waits until its group is gone, then prints "ready" and never drains, so a kill -9 landsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.expect("npx hindwatch --help exits 0", help.code === 0, `${help.stdout.split("\n").length} lines`);Fix: Pin versions and sources; vendor anything fetched at install time.const fix = `start Metro on port ${port} (npx expo start or npx react-native start)`;Fix: Pin versions and sources; vendor anything fetched at install time.* and adb children that stay quiet), then kill -9, recovery, and a graceful stop.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."kill -9",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.const npx = (args: readonly string[], input?: Parameters<typeof run>[2]["input"]) => run("npx", ["--no-install", "hindwatch", ...args], { cwd: app, env, input });Fix: Pin versions and sources; vendor anything fetched at install time.'exec 3<&0 0</dev/null; "$@" 3<&- & c=$!; (read _ <&3; kill $c; sleep 2; kill -9 $c) 2>/dev/null & w=$!; exec 3<&-; ' +Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
7 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim omer-ayhan: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.