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.
npx skills add ur-grue/autopunk-media-skills --skill reader-comments-analyzergit clone --depth 1 https://github.com/ur-grue/autopunk-media-skillsWrote 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.
[](https://agentmods.dev/skills/ur-grue/autopunk-media-skills/reader-comments-analyzer)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/reader-comments-analyzer"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/reader-comments-analyzer/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.
<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/reader-comments-analyzer"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/reader-comments-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00046 | $0.01909 |
| Opus 5 | $0.00023 | $0.00955 |
| Sonnet 5 | $0.00009 | $0.00382 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
reader-comments-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reader Comments Analyzer
What This Skill Does
Reads a batch of reader comments and produces a structured summary of recurring themes, unanswered questions, emotional tone, and actionable editorial signals — so editors and journalists can understand what their audience actually took from a piece.
When To Use This Skill
- After publishing a story that generated significant reader response and you want to understand what landed and what did not
- When deciding whether to follow up on a story based on what readers are asking
- When a piece attracted hostile or polarised comments and you need to understand the pattern before responding
- When commissioning a follow-up or correction and you want to prioritise the issues readers flagged most often
- When an editor wants an audience intelligence report without reading hundreds of individual comments
What You Need To Provide
Required:
- A batch of reader comments (paste them directly — a minimum of 10 is useful; 30 or more gives more reliable patterns)
- The headline or a one-sentence description of the original article (so the assistant can assess relevance and gap between article intent and reader response)
Optional:
- The platform the comments came from (website, YouTube, Facebook, Reddit, etc.) — tone and conventions differ by platform
- Any specific question you want answered (e.g., "What are readers most angry about?" or "What follow-up story ideas are hidden in these comments?")
- Whether you want the analysis to inform a correction, a follow-up article, or a community response
How the Assistant Approaches This
- Reads through all comments and identifies recurring subjects, questions, and emotional registers — grouping similar responses together without losing important outliers
- Assesses the overall tone distribution: what proportion of comments are broadly positive, critical, questioning, hostile, or off-topic
- Extracts the three to five strongest editorial signals: specific factual challenges, gaps the article did not address, misunderstandings the headline or framing may have caused, and story ideas the audience is explicitly requesting
- Flags any comments that suggest a correction may be warranted — factual disputes supported by named sources, direct corrections from people with apparent expertise, or errors the publication has not yet acknowledged
- Summarises findings in a format ready to share with an editorial meeting
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 110 lines · 46 tokens per session scan A d5b3dc777a92
reader-comments-analyzer is a skill published in the GitHub repository ur-grue/autopunk-media-skills (30 stars, last pushed 10d ago), licensed MIT. It adds 46 tokens to every session and 1,909 once invoked, about $0.0002 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.
Other skills, from other repositories
xiaoyuzhou-podcast-notes
A workflow that turns a public Xiaoyuzhou FM podcast episode into structured Markdown notes and a saved transcript. Xiaoyuzhou FM is a Chinese podcast platform.
c-research
Summarize web URLs, PDFs, YouTube videos, and podcasts using the summarize CLI. Instantly extract key points from any content type without manual reading. Useful for research, link digests, and media review.
transcript-ingestion
Transcript ingestion authority — capture, normalize, and prioritize transcripts from YouTube videos, podcast pages, captions, show notes, and transcript-like page content for persona systems, RAG pipelines, and grounded synthesis.
LinkedIn Post Writer
Write LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win…
Tweet Thread Builder
Turn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use…
youtube-seo-video
Advanced single-video SEO analysis covering retention curve diagnosis, intro hook strength, APV vs niche benchmark, entity/semantic coverage, title/description/tags, chapters with Key Moments schema, thumbnail, captions, audio loudness, end-screens, and engagement signals. Use when user says "analyze this video", "why…