Case 00126
A fast, offline static risk analysis CLI for AI agent skill files. Detects malicious instructions, steganographic payloads, and dangerous capability chains.
npx -y skills add knownasnaffy/prompthound --skill case_00126Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use Gemini CLI (@google/gemini-cli) to do web search / fact-finding and return a sourced summary. Use when the user asks “why did X happen today”, “what’s the latest news”, “search the web”, “find sources/links”, or any task requiring up-to-date info. Prefer this over other search tools when Gemini is available but slow; run it with a TTY, wait longer, and verify source quality.
SKILL.md
2.8 KB, as published. Nobody here has run it
Gemini Web Search
Use Gemini CLI to search the web and produce a concise, sourced answer.
Quick workflow
- Formulate a tight query
- Include: entity + ticker/name + date/time window + what you need (%, $, cause, quotes, links)
- Example:
PayPal (PYPL) fell Feb 4 2026: % change, $ change, main catalyst(s), 3 sources
- Run Gemini CLI with a TTY and long timeout Gemini CLI can hang or be slow without a pseudo-TTY.
Preferred (OpenClaw tool call):
- Use
functions.execwithpty: true - Use
timeout300–600s (longer for heavy searches) - Use
yieldMs~10000 thenprocess.polluntil completion
Command template:
~/.npm-global/bin/gemini -p "<prompt>"
If pty:true still behaves poorly, use a pseudo-tty wrapper:
script -q -c "~/.npm-global/bin/gemini -p \"<prompt>\"" /dev/null
- Extract the answer in a structured way Return:
- The key numeric facts (e.g., % move, $ move, close/intraday)
- 2–4 bullets of the main catalyst(s)
- Links (always)
- Quality control (mandatory)
- Prefer: company IR/SEC filing, Reuters, Bloomberg, WSJ/FT, CNBC, reputable outlets.
- Avoid relying on low-quality finance blogs/SEO sites.
- If sources conflict or look unreliable: say so and ask user for a screenshot/link, or re-run with a stricter prompt.
Prompts that work well
-
Fast triage:
Search the web: <topic>. Give 3 bullets + 2 reputable links. -
Market move:
Search the web: Why did <TICKER> move today (<date>)? Provide exact % and $ move (close + intraday if available) and the main catalyst(s). Cite sources with links. -
Force better sources:
Search the web and prioritize Reuters/company IR/SEC filing. If you cannot find them, say so. Topic: <...>. Provide links.
Failure modes & fixes
-
Gemini prints “I will search…” then stalls
- Wait longer (it can be slow).
- Ensure TTY: run with
pty:trueorscript -q -c ... /dev/null.
-
Output has suspicious claims (e.g., odd CEO news)
- Re-run with: “use Reuters/company IR/SEC filing only; otherwise say unknown”.
- Cross-check with at least 2 independent reputable sources.
-
Need numbers but sources don’t show them
- Ask user for the quote/screenshot from their market data app and reconcile.
Local setup notes
- Gemini CLI binary:
~/.npm-global/bin/gemini - Auth: already completed by Jiajie (should work without re-login)