meta-pipe: Skill for Claude Code

.claude/skills/post-to-discussion/SKILL.md

post-to-discussion is a skill for Claude Code from htlin222/meta-pipe. It costs 47 tokens per session (1,304 once invoked), scanned A, original, no licence file.

A way to share a completed meta-analysis project in a GitHub Discussions board. GitHub Discussions is a forum attached to a software repository.

In plain words
What is it for?
Posting completed meta-analysis work or milestone updates to the htlin222/meta-pipe discussions board.
Why use it?
It provides a place to announce project milestones such as a finished analysis or drafted manuscript.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is htlin222/meta-pipe's own configuration. It tells Claude Code how to work on meta-pipe itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything meta-pipe configures →

Reuse

Borrowing it

Nothing to install: this file belongs to htlin222/meta-pipe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/htlin222/meta-pipe/main/.claude/skills/post-to-discussion/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/htlin222/meta-pipe

Made for: Claude Code.

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 post-to-discussion

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/htlin222/meta-pipe/post-to-discussion"><img src="https://agentmods.dev/badge/skills/htlin222/meta-pipe/post-to-discussion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,304 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.
Origin unknown 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.00047 $0.01304
Opus 5 $0.00023 $0.00652
Sonnet 5 $0.00009 $0.00261
Haiku 4.5 $0.00005 $0.00130

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

Security

Grade A, and why

post-to-discussion 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.

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.

.claude/skills/post-to-discussion/SKILL.md · 178 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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 · 178 lines · 47 tokens per session scan A effa935efcaa

Subscribe to this mod's changes

post-to-discussion is a skill published in the GitHub repository htlin222/meta-pipe (123 stars, last pushed today), with no licence file. It adds 47 tokens to every session and 1,304 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

project-graveyard

Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…

Shubhamsaboo/awesome-llm-apps · 127 tokens

commit-archaeologist

Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite…

Shubhamsaboo/awesome-llm-apps · 82 tokens

scope-creep-detector

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too…

Shubhamsaboo/awesome-llm-apps · 98 tokens

mem0-test-integration

Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…

mem0ai/mem0 · 207 tokens

mem0-integrate

Integrate Mem0 into an existing repository using a goal-driven, TDD pipeline. Detects the repo's language automatically and asks the user to pick between Mem0 Platform (managed) and Mem0 Open Source (self-hosted). Writes failing tests before any implementation. Produces a local feature branch plus .mem0-integration/…

mem0ai/mem0 · 188 tokens

marimo-pair

Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.

marimo-team/marimo · 57 tokens