live-comments@r1
VERIFIED· install onlyPublisher claims: "Exposes a read_source tool that lets agents read cited tickets, docs, and files through the same path the checker verifies, so quoted business rules match their sources and stay in sync as those sources or their authors change. It also keeps undecided product decisions explicit as open questions rather than letting agents invent answers." 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 codeAlso atlassian.com, google.com, linear.app, notion.com, notion.so, slack.com, nango.dev — not the publisher's domain; check what for before connecting.
- 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 live-comments@r1 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-11 and scored it 88/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
…e. 4. **Authority.** Draft person definitions from `npx live-comments directory <system>` and `git log` authors, then groups and places from the teams the user describe…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.… members(linear:team/PRICING)`. Get exact ids from `npx live-comments directory <system>` rather than guessing them. Show the definition to the user and add it to `AUTH…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.3. **Sources.** Ask the user which tools their decisions live in, and have them run `npx live-comments connect <system>` for each one.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct."build": "tsc -p tsconfig.json && rm -rf skills && cp -R ../../skills skills && chmod +x dist/main.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.3. **Sources.** Ask the user which tools their decisions live in, and have them run `npx live-comments connect <system>` for each one.Fix: Pin versions and sources; vendor anything fetched at install time.…e. 4. **Authority.** Draft person definitions from `npx live-comments directory <system>` and `git log` authors, then groups and places from the teams the user describe…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.… members(linear:team/PRICING)`. Get exact ids from `npx live-comments directory <system>` rather than guessing them. Show the definition to the user and add it to `AUTH…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- If a ticket, document or file decides the rule, add `@source <ref> ["<quote>"] [by <authority>]`. Read sources only with `npx live-comments read <ref>` and copy quotes exactly from its output.Fix: Pin versions and sources; vendor anything fetched at install time.- Before writing a business rule, run `npx live-comments context <file>:<line>`.Fix: Pin versions and sources; vendor anything fetched at install time.…ined in `AUTHORITY`. When the user says who decides, match their words against `npx live-comments authority`; if no name fits, propose a definition (with exact ids from `npx liv…Fix: Pin versions and sources; vendor anything fetched at install time.1. Run `npx live-comments init`. It creates an empty config and `AUTHORITY` file, installs this skill and registers the MCP server. It makes no choices for the project.Fix: Pin versions and sources; vendor anything fetched at install time.…me fits, propose a definition (with exact ids from `npx live-comments directory <system>`) and add it only after the user agrees. Otherwise reuse the names nearby code …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.1. Run `npx live-comments init`. It creates an empty config and `AUTHORITY` file, installs this skill and registers the MCP server. It makes no choices for the project.Fix: Pin versions and sources; vendor anything fetched at install time.…me fits, propose a definition (with exact ids from `npx live-comments directory <system>`) and add it only after the user agrees. Otherwise reuse the names nearby code …Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- If a ticket, document or file decides the rule, add `@source <ref> ["<quote>"] [by <authority>]`. Read sources only with `npx live-comments read <ref>` and copy quotes exactly from its output.Fix: Pin versions and sources; vendor anything fetched at install time.- If a source is in a tool the project can't read yet, ask the user to run `npx live-comments connect <system>`, and write an `@open` with `in <place>` meanwhile.Fix: Pin versions and sources; vendor anything fetched at install time.5. Add the CI step `init` printed, and run `npx live-comments check`.Fix: Pin versions and sources; vendor anything fetched at install time.…onnect <system>` for each one. 4. **Authority.** Draft person definitions from `npx live-comments directory <system>` and `git log` authors, then groups and places from the team…Fix: Pin versions and sources; vendor anything fetched at install time.3. **Sources.** Ask the user which tools their decisions live in, and have them run `npx live-comments connect <system>` for each one.Fix: Pin versions and sources; vendor anything fetched at install time.- If a source is in a tool the project can't read yet, ask the user to run `npx live-comments connect <system>`, and write an `@open` with `in <place>` meanwhile.Fix: Pin versions and sources; vendor anything fetched at install time.…onnect <system>` for each one. 4. **Authority.** Draft person definitions from `npx live-comments directory <system>` and `git log` authors, then groups and places from the team…Fix: Pin versions and sources; vendor anything fetched at install time.- If a source is in a tool the project can't read yet, ask the user to run `npx live-comments connect <system>`, and write an `@open` with `in <place>` meanwhile.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| `directory <system>` | A connected tool's accounts and places, with exact ids |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.npx live-comments context <file>:<line>Fix: Pin versions and sources; vendor anything fetched at install time.- Ask the user to connect it with `npx live-comments connect <system>`. Connecting needs the user to sign in, so you can't do it for them. Tell them exactly which command to run and why.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.run: npx live-comments check --base origin/\${{ github.base_ref || 'main' }}`Fix: Pin versions and sources; vendor anything fetched at install time.- Ask the user to connect it with `npx live-comments connect <system>`. Connecting needs the user to sign in, so you can't do it for them. Tell them exactly which command to run and why.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.3. **Sources.** Ask the user which tools their decisions live in, and have them run `npx live-comments connect <system>` for each one.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- If a source is in a tool the project can't read yet, ask the user to run `npx live-comments connect <system>`, and write an `@open` with `in <place>` meanwhile.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- Before writing a business rule, run `npx live-comments context <file>:<line>`.Fix: Pin versions and sources; vendor anything fetched at install time.5. Add the CI step `init` printed, and run `npx live-comments check`.Fix: Pin versions and sources; vendor anything fetched at install time.…ined in `AUTHORITY`. When the user says who decides, match their words against `npx live-comments authority`; if no name fits, propose a definition (with exact ids from `npx liv…Fix: Pin versions and sources; vendor anything fetched at install time.npx live-comments context <file>:<line>Fix: Pin versions and sources; vendor anything fetched at install time.…me in the authority file, fully expanded, as JSON. | | `live-comments directory <system>` | yes | List a connected system's accounts (id, display name, email) and place…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| `connect <system>` | Connect a tool through Composio or Nango |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…and place definitions can be written with exact ids. | | `live-comments connect <system> [--via nango\|composio] [--base-url <url>]` | yes | Connect a tool through a tr…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.