Skills/ClawHub/defi-yield-monitor

defi-yield-monitor@1.1.0

VERIFIED· install only

Publisher claims: "Monitor DeFi lending and savings positions across Aave v3, SparkLend, Spark Savings, and Kamino with balances, APYs, health factors, and yield tracking." Observed in sandbox: calls github.com only, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher reed1898 · publishing for 255 daysInstalls 1,404Last detonated 56 min ago
$clawhub install defi-yield-monitor
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 1 of 1 bundled script run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: calls github.com only, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 2 s · 3 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
1.0sfilesystemread ~/.openclaw/workspace/projects/defi-yield-monitor/.git/config · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/packed-refs · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/HEAD · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/refs/ · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/info/grafts · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/shallow outside project
1.0sfilesystemwrote ~/.openclaw/workspace/projects/defi-yield-monitor/.git/info/exclude · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/hooks/pre-rebase.sample · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/hooks/push-to-checkout.sample · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/hooks/fsmonitor-watchman.sample · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/hooks/pre-applypatch.sample · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/hooks/update.sample
1.0snetworkCONNECT tcp://github.com:443
1.0sprocessexec /usr/bin/git
1.0sprocessexec /usr/lib/git-core/git
1.0sprocessexec /usr/lib/git-core/git-remote-https
1.0sprocessexited 1: Cloning into '/tmp/ks-detonate-0b6eQQ/setup/home/.openclaw/workspace/projects/defi-yield-monitor'...
1.0sprocessbundled script run in the sandbox with no arguments
1.0sprocessexited 1:
1.0sprocess1 of 1 bundled script run with no arguments
1.0sprocessscript backend runs setup only
1.0sprocessscript backend runs setup only
1.6sprocesssecond launch, clock +45 days, CI unset
2.2sfilesystemread ~/.openclaw/workspace/projects/defi-yield-monitor/.git/HEAD outside project
2.2sfilesystemwrote ~/.openclaw/workspace/projects/defi-yield-monitor/.git/objects/maintenance.lock · ~/.openclaw/workspace/projects/defi-yield-monitor/.git/ORIG_HEAD.lock
2.2snetworkCONNECT tcp://github.com:443
2.2sprocessexec /usr/bin/git
2.2sprocessexec /usr/lib/git-core/git
2.2sprocessexec /usr/lib/git-core/git-remote-https
2.2sprocessexec .venv/bin/pip
2.2sprocessexited 127: ./scripts/setup.sh: line 26: .venv/bin/pip: No such file or directory

Static findings

No findings across 232 lines in 4 files.

Cost to the agent

Instructions loaded
≈799 tok
1 file · 4 in bundle

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.