discussion-commenter

discussion-commenter is a skill for Claude Code, Codex from pamelafox/presentation-skills. It costs 35 tokens per session (302 once invoked), scanned A, original, MIT.

A tool that turns question-and-answer sections from a Markdown writeup into comments on a GitHub Discussion. Markdown is a plain-text format commonly used for documentation.

In plain words
What is it for?
Use it to parse dated Q&A sections from a writeup, preview the comments with a dry run, and post them to a GitHub Discussion with the GitHub CLI.
Why use it?
It saves you from copying each writeup section into a discussion manually and keeps the comment format consistent.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to parse dated Q&A sections from a writeup, preview the comments with a dry run, and post them to a GitHub Discussion with the GitHub CLI.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pamelafox/presentation-skills/discussion-commenter
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 pamelafox/presentation-skills --skill discussion-commenter
Clone the repo
git clone --depth 1 https://github.com/pamelafox/presentation-skills

Made for: Claude Code, Codex.

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 discussion-commenter

README.md
[![agentmods](https://agentmods.dev/badge/skills/pamelafox/presentation-skills/discussion-commenter/github.svg)](https://agentmods.dev/skills/pamelafox/presentation-skills/discussion-commenter)
Your own site
<a href="https://agentmods.dev/skills/pamelafox/presentation-skills/discussion-commenter"><img src="https://agentmods.dev/badge/skills/pamelafox/presentation-skills/discussion-commenter/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 discussion-commenter

Your own site · 80×15
<a href="https://agentmods.dev/skills/pamelafox/presentation-skills/discussion-commenter"><img src="https://agentmods.dev/badge/skills/pamelafox/presentation-skills/discussion-commenter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 302 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.00035 $0.00302
Opus 5 $0.00017 $0.00151
Sonnet 5 $0.00007 $0.00060
Haiku 4.5 $0.00003 $0.00030

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

Security

Grade A, and why

discussion-commenter 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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (post_qas.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/discussion-commenter/SKILL.md · 47 lines

What it actually says

Discussion Commenter

Post Q&A entries from markdown writeups as individual comments to a GitHub Discussion.

Usage

Run the script with the writeup file path, discussion URL, and date:

uv run .agents/skills/discussion-commenter/post_qas.py \
  "path/to/writeup.md" \
  "https://github.com/orgs/ORG/discussions/NUMBER" \
  "2026/01/06"

Arguments

  1. writeup_path - Path to the markdown writeup file containing Q&As
  2. discussion_url - Full URL to the GitHub discussion
  3. date - Date string to prefix each comment (e.g., "2026/01/06")

Options

  • --dry-run - Parse and display what would be posted without actually posting

Requirements

  • GitHub CLI (gh) must be installed and authenticated
  • User must have permission to comment on the discussion

Output

Each ## Question section in the writeup becomes a separate comment, formatted as:

**2026/01/06: Question Title**

Answer content...

Subsections (### Follow-up) are included in the parent question's comment.

Files

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.

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. 10d ago First seen · 47 lines · 35 tokens per session scan A 07611c932ce0

Subscribe to this mod's changes

discussion-commenter is a skill published in the GitHub repository pamelafox/presentation-skills (117 stars, last pushed 7d ago), licensed MIT. It adds 35 tokens to every session and 302 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.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens