Individual skill
investigation-report
One-shot Base-token investigation - runs any subset of six onchain-security checks (rug-scan, contract-audit, deployer-trace, holder-concentration, honeypot, lp-lock) into one verdict. Keyless core.
skills/investigation-report/SKILL.md
Source commit 25575a6be3bfab41925964de55654056a2fe0c39
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 789
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude-code Repository topic
- agent-framework Repository topic
- agents Repository topic
- ai Repository topic
- anthropic Repository topic
- claude Repository topic
- harness Repository topic
- llm Repository topic
- automation Repository topic
- crypto Declared skill tag
- security Declared skill tag
- base Declared skill tag
- security Derived category
- legal Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytesSKILL.mdcore · 28,506 bytes
Read excerpt
> **${var}** — Base subject to investigate, plus optional flags: `<token-address> [--checks=rug,contract,deployer,holders,honeypot,lp] [--depth=quick|deep]`. The first token is the subject contract address (`0x…`, required). `--checks=` is a comma-list selecting which analyzers to run (**default = all six**). `--depth=` is `quick` (the old rug-scan fast path — minimal reads) or `deep` (full standalone logic of each selected check; **default**). If the subject address is empty, log `REPORT_NO_TARGET` and exit cleanly (no notify).
>
> Examples:
> - `0xToken` → all six checks, deep report.
> - `0xToken --checks=honeypot` → only the honeypot simulation (reproduces the standalone honeypot-check exactly, incl. its `HONEYPOT_*` end-states).
> - `0xToken --checks=rug,lp --depth=quick` → rug verdict + LP-lock, fast path.
> - `0xToken --checks=contract,deployer,holders --depth=deep` → structural audit + deployer entity intel + full concentration.
The "tell me everything about this token" skill. Instead of running six checks by hand, this composes them into one structured report behind a selector: **rug risk**, **contract audit** (verification / owner powers / proxy), **deployer trace** (who shipped it and their history), **holder concentration** (whale risk), **honeypot** (can you actually sell?), and **LP lock** (can the team pull liquidity?) — with a one-line summary on top.
Designed to **degrade gracefully**: each selected section runs independently, so a section that needs a key (or returns nothing) is marked `unavailable` without aborting the rest. Selecting a single check makes the composite behave as that one analyzer — same steps, same thresholds, same notify format, same status codes.
## Config
- Subject = the first token of `${var}` (validate: `0x` + 40 hex). Chain = Base (`chainid=8453`, explorer `basescan.org`).