kitsmith@0.1.0
VERIFIED· install onlyPublisher claims: "Enables coding agents to build UI from a chosen React component kit by finding components by intent, reading their exact props, following composition recipes, and validating the result against the kit's real types. Kit-specific knowledge lives in swappable adapters, so the same tools work with any React kit, with Ant Design supported out of the box." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-14 and scored it 91/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 · 0 s · 1 scenarios · 0 deviationsStatic findings
/** How an agent host should start the server: via npx when installed from npm, else straight from this checkout. */Fix: Pin versions and sources; vendor anything fetched at install time.write("AGENTS.md", upsertBlock(readIfExists(path.join(projectDir, "AGENTS.md")), block));Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.else if (!/^@AGENTS\.md\s*$/m.test(claude)) write("CLAUDE.md", `${claude.replace(/\s*$/, "")}\n\[email protected]\n`);Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.if (claude === undefined) write("CLAUDE.md", "@AGENTS.md\n");Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.it("uses npx when the package lives inside node_modules", () => {Fix: Pin versions and sources; vendor anything fetched at install time.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.