active-listening marketplace

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Security

Grade A, and why

active-listening marketplace scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

.claude-plugin/marketplace.json · 24 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
  "name": "active-listening",
  "owner": {
    "name": "Harsh Joshi",
    "url": "https://github.com/josharsh"
  },
  "metadata": {
    "description": "Detects your preferences during conversation and remembers them across sessions",
    "version": "1.0.0"
  },
  "plugins": [
    {
      "name": "active-listening",
      "description": "Monitor conversation to detect user preference statements, save them to disk, review saved preferences, and apply learned rules in every future session",
      "source": "./",
      "license": "MIT",
      "category": "productivity",
      "keywords": ["preferences", "memory", "active-listening", "claude-code"],
      "skills": ["./skills/active-listening"]
    }
  ]
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

Related

Other plugins, from other repositories