saybooks@0.4.0
VERIFIED· install onlyPublisher claims: "Enables an AI agent and a human interface to share one command registry and audit trail for invoicing, order-to-cash, CRM, purchasing, inventory, job hunt, and personal-finance workflows, with guards that enforce permissions and business rules." 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Not enough was observed to say yet. Nothing executable in the bundle ran; the trace covers the install step only. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try saybooks` runs it now and prints the full answer.
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-07 and scored it 85/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
<link rel="icon" type="image/svg+xml" href="/favicon.svg"><link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@400;500;600;700&display=swap"><style>Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<link rel="preconnect" href="https://fonts.googleapis.com"><link rel="preconnect" href="https://fonts.gstatic.com" crossorigin><link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=FraFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const existing = wsp.use(WS, () => H.db().prepare('SELECT COUNT(*) c FROM hunt_posting').get().c);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.postings: H.db().prepare(`SELECT p.id, p.title, p.status, p.req_id, p.location, c.name AS company FROM hunt_posting p JOIN hunt_company c ON c.id = p.company_idFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(` postings: ${report.postings} (guard raised ${report.warnings} warnings during replay — same reqs via multiple agencies, as expected)`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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.