responsive-agent@1.8.1
CAUTION· static onlyPublisher claims: "Enables a two-layer agent pattern where the main process never blocks by spawning subagents for long, remote, or uncertain tasks, ensuring constant responsiv..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-15 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Instructs the agent to modify its persistent memory or instruction files; Instructs the agent to modify its persistent memory or instruction files; Instructs the agent to modify its persistent memory or instruction files. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
- **`timeout`**: hard kill after N seconds. Command is killed if it exceeds this.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.- No automatic kill — let it finish unless user cancelsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.If significant → write to MEMORY.mdFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.(kill config-sync subagent)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.**Main process handles MEMORY.md writes** — subagent reports the result, main process decides whether to write it down.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| Result Type | Update MEMORY.md? | Example |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- **timeout** = hard kill after N seconds. Must be > yieldMs.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.| Unknown duration | 30000 | 600 | Conservative — bg after 30s, kill at 10min |Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.### When to Update MEMORY.mdFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.**After subagent completes:** if the task resulted in a **decision, config change, or state change**, update `MEMORY.md`.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
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.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim guytogay: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.