ServiceNow Agent
v0.1.1Read-only CLI access to ServiceNow Table, Attachment, Aggregate, and Service Catalog APIs; includes schema inspection and history retrieval (read-only).
⭐ 1· 2.1k·1 current·1 all-time
bySeth Rose@thesethrose
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's stated purpose is a read-only ServiceNow CLI and the included cli.mjs implements read operations using Basic Auth; requiring only 'node' as a binary is reasonable. However the published registry metadata lists no required environment variables or primary credential while SKILL.md and cli.mjs clearly expect SERVICENOW_DOMAIN, SERVICENOW_USERNAME, and SERVICENOW_PASSWORD (or equivalent flags). That metadata mismatch is an incoherence — a consumer would legitimately expect the skill to declare the required credentials up front.
Instruction Scope
SKILL.md instructs the agent to read a .env file in the skill folder and to use the bundled CLI for GET-only requests. cli.mjs does read .env via loadDotEnv and will read any batch JSON file path supplied (relative to cwd or absolute). Reading a .env and user-provided JSON files is expected for this CLI, but be aware the tool will read any file path you give it (so don't pass sensitive local files). The skill advertises 'read-only' but some included OpenAPI reference files describe POST/PUT/DELETE endpoints — the CLI code itself enforces GET-only usage, but the presence of write-capable reference documents is an inconsistency to note.
Install Mechanism
There is no install spec (instruction-only + included script) and the only required binary is node. No external downloads or archive extraction are present in the package, which is low risk from an installer perspective.
Credentials
The skill requires ServiceNow credentials (domain, username, password) to function, yet the registry metadata does not declare any required environment variables or primary credential — this is a meaningful mismatch. The SKILL.md recommends storing credentials in a .env file inside the skill folder (plaintext), which is insecure practice unless the user understands and accepts the risk. No other unrelated credentials are requested.
Persistence & Privilege
The skill does not request persistent presence (always:false), does not modify other skills or system-wide settings, and does not install background services. It runs on-demand as a CLI script, which is proportionate to its functionality.
What to consider before installing
Before installing, verify and correct the credential metadata mismatch: the skill needs SERVICENOW_DOMAIN, SERVICENOW_USERNAME, and SERVICENOW_PASSWORD (or you must pass them on the command line). Use a least-privileged ServiceNow account scoped to read-only access and avoid saving production passwords in plaintext .env files — consider using runtime flags or a secrets store instead. Inspect cli.mjs yourself (it is included) to confirm only GET requests are made in your use cases. Note the package includes OpenAPI reference files that mention POST/DELETE endpoints; those are not used by the CLI but are an inconsistency to be mindful of. If you do proceed, run the tool in an isolated/test environment first and rotate or revoke the credentials after testing. If you need higher assurance, ask the publisher to update registry metadata to declare required env vars and to document why reference files include write endpoints even though the CLI is read-only.Like a lobster shell, security has layers — review code before you run it.
latestvk9719x28tvhx3s5c5ggdda1g1n7z977m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🧾 Clawdis
Binsnode