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 kakutixyz-ai/agent-publishing-skills --skill github-discussionsgit clone --depth 1 https://github.com/kakutixyz-ai/agent-publishing-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/kakutixyz-ai/agent-publishing-skills/github-discussions)<a href="https://agentmods.dev/skills/kakutixyz-ai/agent-publishing-skills/github-discussions"><img src="https://agentmods.dev/badge/skills/kakutixyz-ai/agent-publishing-skills/github-discussions/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/kakutixyz-ai/agent-publishing-skills/github-discussions"><img src="https://agentmods.dev/badge/skills/kakutixyz-ai/agent-publishing-skills/github-discussions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00645 |
| Opus 5 | $0.00000 | $0.00322 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
github-discussions 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 9d 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.
This is a copy
83% identical to a-list-apart — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: writer-platform-github-discussions description: Write platform-specific drafts for GitHub Discussions using its dedicated language, length, tone, format, and community rules.
GitHub Discussions Writer
Use this skill when the target platform is github-discussions / GitHub Discussions. This is the platform-specific writing capability for that website, not a generic adapter.
Knowledge To Load
knowledge/platforms/github-discussions.mdskills/adapter-community-discussion/SKILL.mdknowledge/styles/community-post.mdtemplates/base/discussion.mdtemplates/platforms/github-discussions/when a platform override template existsknowledge/rules/anti-spam.mdknowledge/rules/no-auto-publish.mdknowledge/rules/disclosure.mdknowledge/rules/factual-accuracy.md
Inputs
- Project brief matching
schemas/project-brief.schema.json, or a base draft matchingschemas/platform-draft.schema.json. - Any user-provided assets, links, screenshots, metrics, code snippets, or launch details.
Platform Binding
- Platform slug:
github-discussions - Recommended adapter:
adapter-community-discussion - Primary language code:
en - Categories: community-discussion
- Target audience: developers
Writing Contract
- Load
knowledge/platforms/github-discussions.mdfirst and treat it as the source of truth for this website. - Extract the site's required language, regional spelling, expected length, tone, accepted content shapes, formatting conventions, required assets, and banned patterns.
- Use
adapter-community-discussiononly as a helper pattern. If the generic adapter conflicts withgithub-discussions, the platform profile wins. - Match the site's expected content length. Short-post platforms must stay short; long-form editorial or tutorial platforms must provide enough depth, evidence, and structure.
- Match the site's voice. Preserve literary, technical, formal, skeptical, educational, founder-led, visual, or community-native tone when the profile asks for it.
- Use only facts from the brief, base draft, loaded knowledge, templates, and user-provided materials. Do not invent URLs, metrics, version numbers, names, screenshots, testimonials, or claims.
- Include required placeholders only when a platform field is mandatory but the fact is missing, and set
statustoneeds_review. - Remove content types listed as poor fit for this platform. If the project is fundamentally unsuitable, return a
needs_reviewdraft explaining the fit problem instead of forcing a post. - Do not publish or imply that publication has happened.
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.
- 9d ago First seen · 56 lines · 0 tokens per session scan A 1992f74cf19c
github-discussions is a skill published in the GitHub repository kakutixyz-ai/agent-publishing-skills (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 645 tokens. A static security scan graded it A with 0 findings. It is 83% identical to a-list-apart, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…