Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/pc035860/skill-output-style-to-plugin/output-style-to-plugin)<a href="https://agentmods.dev/skills/pc035860/skill-output-style-to-plugin/output-style-to-plugin"><img src="https://agentmods.dev/badge/skills/pc035860/skill-output-style-to-plugin/output-style-to-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/pc035860/skill-output-style-to-plugin/output-style-to-plugin"><img src="https://agentmods.dev/badge/skills/pc035860/skill-output-style-to-plugin/output-style-to-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.00051 | $0.02086 |
| Opus 5 | $0.00026 | $0.01043 |
| Sonnet 5 | $0.00010 | $0.00417 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
output-style-to-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 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convert deprecated Claude Code output style markdown files into properly structured plugins using SessionStart hooks. This skill handles the complete conversion process automatically, requiring only essential information from the user.
When to Use This Skill
Use this skill when:
- Converting an existing output style
.mdfile to plugin format - Migrating from the deprecated
outputStyleconfiguration to the plugin system - Setting up a new plugin-based output style from scratch
- User asks to "convert output style to plugin" or similar migration requests
Conversion Workflow
Step 1: Gather Required Information
Ask the user for essential information before starting the conversion. Use the AskUserQuestion tool to collect:
- Output Style File: Path to the existing output style
.mdfile - Plugin Name: Identifier for the plugin (suggest kebab-case version of file name)
- Plugin Description: Brief description (can extract from output style frontmatter if present)
- Version: Default to "1.0.0" for initial conversion
- Author Name: Plugin author's name
- Author Email (optional): Author's email address
Example questions:
Question: "What is the path to your output style markdown file?"
Question: "What would you like to name this plugin? (e.g., 'my-output-style')"
Question: "Brief description of this output style?"
Question: "Author name for the plugin?"
Question: "Author email? (optional, press Enter to skip)"
Step 2: Check for Existing Marketplace
Before creating a new marketplace, check if the user has an existing marketplace they want to use:
- Ask: "Do you have an existing marketplace you'd like to add this plugin to?"
- If yes:
- Ask for marketplace path
- Read the existing
marketplace/.claude-plugin/marketplace.json - Extract marketplace name and owner information
- Plan to add plugin entry to existing plugins array
- If no:
- Collect marketplace information:
- Marketplace name (suggest based on user context)
- Owner name (suggest same as plugin author)
- Owner email (suggest same as plugin author email)
- Plan to create new marketplace structure
- Collect marketplace information:
What ships with it
7 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.
- 11d ago First seen · 278 lines · 51 tokens per session scan A fd03390123c9
output-style-to-plugin is a skill published in the GitHub repository pc035860/skill-output-style-to-plugin (2 stars, last pushed 10mo ago), licensed MIT. It adds 51 tokens to every session and 2,086 once invoked, about $0.0003 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-31.
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…