nm-memory-palace-knowledge-intake@1.9.19
CAUTION· static onlyPublisher claims: "Processes external resources into stored knowledge with quality scoring and routing" 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-08 and scored it 71/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: Coercive compliance language. 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
When the evaluation score is 80-100 (evergreen), youFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- [Rule 6: Ask Yourself If It Sparks Joy](https://konmari.com/marie-kondo-rules-of-tidying-sparks-joy/)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
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim athola: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.