Agent skill
opencrow-osint-toolbox
Use the OpenCROW OSINT stack for username enumeration, archive lookup, and public search workflows. Use when Codex needs `sherlock`, `waybackpy`, `shodan`, or when a full install tracks manual theHarvester setup.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/opencrow-osint-toolbox
SKILL.md
OpenCROW OSINT Toolbox
Use this skill for challenges that depend on public-source reconnaissance rather than direct target exploitation. It covers username hunting with sherlock, historical site lookups with waybackpy, and Shodan-backed discovery with the shodan CLI and Python client.
Quick Start
Start the MCP server from the installed CLI:
opencrow-osint-mcp
Verify the mapped stack:
python ~/.codex/skills/opencrow-osint-toolbox/scripts/verify_toolkit.py
Workflow
- Use
sherlockfor username reuse checks across public services. - Use
waybackpywhen the clue may exist in an archived site snapshot. - Use
shodanwhen the problem involves public internet exposure, banners, or service fingerprints. - If a full profile was installed, treat theHarvester as a manual follow-up tool from the installer summary.
- Prefer the MCP server operations first:
toolbox_info,toolbox_verify,toolbox_capabilities,osint_username_lookup,osint_archive_lookup, andosint_shodan_lookup.
Resources
opencrow-osint-mcp: stdio MCP server for typed username, archive, and Shodan lookups.scripts/verify_toolkit.py: confirm that the mapped OSINT tools are installed.references/tooling.md: quick guidance for choosing OSINT tools.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?