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 gobing-ai/superskill --skill openai-publish-plugingit clone --depth 1 https://github.com/gobing-ai/superskillWrote 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/gobing-ai/superskill/openai-publish-plugin)<a href="https://agentmods.dev/skills/gobing-ai/superskill/openai-publish-plugin"><img src="https://agentmods.dev/badge/skills/gobing-ai/superskill/openai-publish-plugin/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/gobing-ai/superskill/openai-publish-plugin"><img src="https://agentmods.dev/badge/skills/gobing-ai/superskill/openai-publish-plugin.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.00062 | $0.01376 |
| Opus 5.5 | $0.00025 | $0.00550 |
| Sonnet 5.5 | $0.00012 | $0.00275 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
openai-publish-plugin 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 26d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish a plugin to OpenAI
Carry the authorized release through preparation, upload, review, and publication. Use the project's identity, build system, and publisher facts. Report the saved portal state at every handoff; a successful upload does not establish publication.
1. Establish the release
- Read project instructions, the plugin manifest, build configuration, and git status. Identify the source directory, internal name, display name, version, target host, and prerequisites. Preserve unrelated changes.
- Check the current official submission guide and package guide. For a Claude Code source, also check the conversion guide. Portal fields, eligibility, formats, and release rules can change.
- Reuse publisher, country availability, commerce, and contact choices already
confirmed in this session. Ask only for missing facts. Gobing AI uses
[email protected]publicly; other publishers supply their own contact. - If
plugin-creator:prepare-plugin-submissionis available, follow it for general submission requirements. Otherwise use the official guides directly. This skill supplies the project and browser handoff; it needs no extra plugin.
2. Identify what runs
- A skills-only plugin does not need an invented MCP server. If the plugin actually uses remote tools, document its real endpoint, authentication, and reviewer access using the current MCP requirements.
- For a local CLI, disclose installation, supported versions, permissions, and required environment variables. Exercise the documented path in a clean environment where feasible; never claim ChatGPT can execute a local CLI because Codex can. Do not silently remove essential functionality to qualify.
- If the current conversion guide directs plugins whose core behavior requires local execution, arbitrary filesystem access, hardware, or offline operation to contact OpenAI, follow that eligibility route before submission. Another plugin reaching review is not proof of eligibility for this one.
What ships with it
4 files 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.
- 26d ago First seen · 120 lines · 62 tokens per session scan A e1033b65cf67
openai-publish-plugin is a skill published in the GitHub repository gobing-ai/superskill (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 62 tokens to every session and 1,376 once invoked, about $0.0002 per session on Opus 5.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-10-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.