agentmods.dev

moonshine-listen

moonshine-listen is a skill for Claude Code from enjalot/moonshine. It costs 69 tokens per session (1,483 once invoked), scanned A, original, MIT.

A listener for authorship comments from the Moonshine article HUD, a project feedback display. It checks feedback inboxes periodically and can hand comments to the authoring workflow.

In plain words
What is it for?
Run it on a loop to monitor one Moonshine project or all available projects, show live status, and process accumulated comments when requested.
Why use it?
It helps catch feedback that arrives while the coding session is idle, instead of waiting for the next interaction.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; $skill-name invocation.

Part of the moonshine plugin — 5 skills, 1 hook shipped together

not rated 52repo 25d ago A scan SkillSpector: pass 69 tokens original MIT

Good fit Run it on a loop to monitor one Moonshine project or all available projects, show live status, and process accumulated comments when requested.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/enjalot/moonshine/moonshine-listen
View source ↗ enjalot/moonshine
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.

Any agent
npx skills add enjalot/moonshine --skill moonshine-listen
Clone the repo
git clone --depth 1 https://github.com/enjalot/moonshine

Made for: Claude Code.

Or install moonshine, the plugin that ships this one along with the rest of its 5 skills, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for moonshine-listen

README.md
[![agentmods](https://agentmods.dev/badge/skills/enjalot/moonshine/moonshine-listen/github.svg)](https://agentmods.dev/skills/enjalot/moonshine/moonshine-listen)
Your own site
<a href="https://agentmods.dev/skills/enjalot/moonshine/moonshine-listen"><img src="https://agentmods.dev/badge/skills/enjalot/moonshine/moonshine-listen/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for moonshine-listen

Your own site · 80×15
<a href="https://agentmods.dev/skills/enjalot/moonshine/moonshine-listen"><img src="https://agentmods.dev/badge/skills/enjalot/moonshine/moonshine-listen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,483 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00069 $0.01483
Opus 5 $0.00034 $0.00741
Sonnet 5 $0.00014 $0.00297
Haiku 4.5 $0.00007 $0.00148

Measured 11d ago against content hash 6d7400e15089, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

moonshine-listen 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 11d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/moonshine/skills/moonshine-listen/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

moonshine-listen — authorship feedback listener (Claude Code adapter)

This is the idle-coverage half of the moonshine authorship-feedback loop (plugins/moonshine/FEEDBACK.md). The Stop hook already handles delivery at turn boundaries; this skill covers requests that land while the session is idle, and powers the HUD's live status (the heartbeat) and its mode controls (the control.json it reads). Note the default mode is accumulate: comments pile up and are only drained when the author presses Address in the HUD (address.json) or has opted into continuous auto-address (listen).

Each invocation performs one tick. Run it under /loop so the ticks repeat.

Scope

  • If invoked with a project name argument, operate on ~/.agent/moonshine/<arg>/.feedback/ only.
  • Otherwise operate on every existing ~/.agent/moonshine/*/.feedback/ inbox.
  • If MOONSHINE_FEEDBACK=off is set in the environment, do nothing and end the loop — the same kill switch the Stop hook and the dev server honor.

Use absolute, ISO-8601 UTC timestamps (date -u +%Y-%m-%dT%H:%M:%SZ) everywhere.

One tick

For each in-scope .feedback/ directory:

  1. Manifest. If adapter.json is missing, write {"harness":"claude-code","version":"adapter","installedAt":"<now>"}.

  2. Read control. Read control.json; treat a missing file as {"mode":"accumulate"} (the default: hold comments, don't drain).

    • If mode == "stopped" and there is no address.json: write a final heartbeat.json with "mode":"stopped" and the current ts, then end — do not schedule another tick for this project. (If all in-scope projects are stopped, end the loop entirely; tell the user the listener stopped.)

  3. Route to the authoring session. Read the optional sessionId from address.json (for a one-shot request), or from control.json when mode is listen. Compare it with $CLAUDE_CODE_SESSION_ID. If the request names a different session — or names one but the current session ID is unavailable — skip this project entirely and do not consume its request. Legacy files without a sessionId remain unscoped.

Read the full file on GitHub · 108 lines

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.

  1. 11d ago First seen · 108 lines · 69 tokens per session scan A 6d7400e15089

Subscribe to this mod's changes

moonshine-listen is a skill published in the GitHub repository enjalot/moonshine (52 stars, last pushed 25d ago), licensed MIT. It adds 69 tokens to every session and 1,483 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens