Skills/npm/taskbean

taskbean@0.7.0

VERIFIED· install only

Publisher claims: "Task management CLI for AI coding agents. Push tasks from Copilot, Claude, or any agent." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher taskbean · publishing for 211 daysInstalls 275Last detonated 33 min ago
$claude mcp add taskbean -- npx -y taskbean
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 · 8 of 42 bundled scripts run with no arguments (the rest were not run: per-bundle cap), 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-22 and scored it 83/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: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 3 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.1sfilesystemwrote ~/.taskbean/.install-channel
0.1sprocessbundled script run in the sandbox with no arguments
0.2sfilesystemwrote ~/.taskbean/.install-channel
0.2sprocessbundled script run in the sandbox with no arguments
0.3sprocessexited 1: Node.js v22.23.5
0.3sprocessbundled script run in the sandbox with no arguments
0.4sprocessbundled script run in the sandbox with no arguments
0.5sprocessbundled script run in the sandbox with no arguments
0.6sprocessbundled script run in the sandbox with no arguments
0.7sprocessbundled script run in the sandbox with no arguments
0.8sprocessbundled script run in the sandbox with no arguments
0.9sprocess8 of 42 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.9sprocessscript backend runs setup only
0.9sprocessscript backend runs setup only
1.0sprocesssecond launch, clock +45 days, CI unset
1.1sfilesystemwrote ~/.taskbean/.install-channel

Static findings

LOW
Refusal suppressionREADME.md:175 · Refusal suppression — attempting to prevent safety responses · informational: not an instruction fileTaskbean 0.5.2 and earlier do not refuse drift: their `bean rebuild --write`Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
LOW
Unpinned dependencysrc/commands/upgrade.js:456 · Unpinned dependencyhint: 'Could not determine whether taskbean was installed via npm or as a standalone binary. Reinstall with the official installer, or run `npm install -g taskbean@latest` manually.',Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06
LOW
Unpinned dependencyscripts/postinstall.cjs:5 · Unpinned dependency// route through `npm install -g taskbean@latest`.Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06
LOW
Unpinned dependencysrc/commands/upgrade.js:276 · Unpinned dependency? ['/d', '/s', '/c', 'npm install -g taskbean@latest']Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06

Cost to the agent

Instructions loaded
≈46 tok
1 file · 45 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for taskbean@0.7.0 as of 2 min ago. This is the package itself, not its dependencies.