Agent Backlink Network
v0.1.0Decentralized backlink exchange for AI agents. Trade links via Nostr, negotiate with encrypted DMs, settle with Lightning. No middlemen.
⭐ 1· 1.7k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The code (register, query, dm, lightning, verify) clearly implements a Nostr-backed backlink exchange with encrypted DMs and optional Lightning payments — this matches the skill name and description. However, the registry metadata claims no required environment variables or primary credential even though the code expects a Nostr private key (nsec) and optionally a Lightning config (.secrets/lightning.json). That metadata omission is an inconsistency.
Instruction Scope
Runtime instructions and SKILL.md are scoped to the stated purpose: generate/load a Nostr private key, query/publish events to Nostr relays, send/receive encrypted DMs, optionally create/pay Lightning invoices, and verify backlinks by crawling pages. The instructions reference local secrets (.secrets/*) and public relays only — there are no instructions to read unrelated system files or exfiltrate arbitrary data.
Install Mechanism
There is no external download/installer in the registry entry; this is an instruction+npm package style module (package.json provided). No hostile install mechanism (no URL downloads or extract steps). Dependencies are reasonable for the task (nostr-tools). Puppeteer appears as a devDependency for verification tests; that is not an elevated install mechanism but may require extra packages if used.
Credentials
The skill needs sensitive secrets: a Nostr private key (nsec) for signing/publishing events and optionally Lightning credentials (LNbits API key or other provider) for payments. Those are proportionate to the functionality (Nostr signing and Lightning payments), but the skill metadata advertised 'no required env vars / no primary credential' which is incorrect. The omission could trick less-technical users into installing without understanding they must provide private keys. Be cautious: publishing signed events with your private key is a strong privilege and Lightning API keys control funds.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide config. It reads local .secrets files and environment variables for credentials (expected for this use). Autonomous invocation is allowed by default (normal for skills), but this is not combined with 'always' or other elevated privileges.
What to consider before installing
What to consider before installing and using this skill:
- The code legitimately requires a Nostr private key (nsec) to sign and publish events and optionally a Lightning API key/config for payments. The registry metadata did NOT declare these required credentials — do not assume no secrets are needed.
- If you try it, use a throwaway/agent-specific Nostr keypair (not your personal/multi-use key) so you don't expose a critical identity if something goes wrong. The SKILL.md and code instruct saving nsec in .secrets/nostr.json or NOSTR_PRIVATE_KEY.
- For Lightning, prefer a wallet/provider account with limited privileges (e.g., an invoice-only key or a separate agent wallet) rather than your primary funds. Review .secrets/lightning.json usage in src/lightning.js to understand which API keys are needed and what they can do.
- The skill will publish events to public Nostr relays you can't control. Anything you register (site info, bids) is publicly broadcast. Do not include private contact details or credentials in registrations or messages.
- The verify flow crawls partner pages (network requests). If you run verification in an environment with elevated network or file access, consider isolating it (container or restricted VM).
- Review the included source files yourself (or have a developer review them) before providing secrets. The code is readable and matches the described functionality, but the metadata omission is a red flag for sloppy packaging and could confuse non-technical users.
- If you want to proceed safely: (1) run in an isolated agent environment, (2) use ephemeral/test keys, (3) audit the lightning provider permissions, and (4) consider limiting the skill's autonomous invocation or requiring explicit user confirmation before publishing or paying.Like a lobster shell, security has layers — review code before you run it.
latestvk975eeegm58e7ct49z4j625k3180cxz4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
