conversation-to-skill

conversation-to-skill is a skill for Codex from Undertone0809/rudder. It costs 113 tokens per session (3,057 once invoked), scanned A, original, Apache-2.0.

A tool for turning the workflow from a conversation into a reusable skill, which is a set of instructions an agent can follow later.

In plain words
What is it for?
Use it to package a working collaboration pattern, standardize a type of task, or improve a draft skill with testing and feedback.
Why use it?
It separates repeatable steps from one-off discussion so a successful process can be used consistently in future tasks.

Skill for Codex

Written for Codex: reads ~/.codex or $CODEX_HOME. Also seen: mentions Codex.

Good fit Use it to package a working collaboration pattern, standardize a type of task, or improve a draft skill with testing and feedback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/undertone0809/rudder/conversation-to-skill
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 Undertone0809/rudder --skill conversation-to-skill
Clone the repo
git clone --depth 1 https://github.com/Undertone0809/rudder

Made for: 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 conversation-to-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/undertone0809/rudder/conversation-to-skill/github.svg)](https://agentmods.dev/skills/undertone0809/rudder/conversation-to-skill)
Your own site
<a href="https://agentmods.dev/skills/undertone0809/rudder/conversation-to-skill"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/conversation-to-skill/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 conversation-to-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/undertone0809/rudder/conversation-to-skill"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/conversation-to-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 113 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,057 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 warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 9
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Excessive Agency · line 154
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00113 $0.03057
Opus 5 $0.00056 $0.01528
Sonnet 5 $0.00023 $0.00611
Haiku 4.5 $0.00011 $0.00306

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

Security

Grade A, and why

conversation-to-skill 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 11 executable files (eval-viewer/generate_review.py, scripts/__init__.py, scripts/aggregate_benchmark.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.

server/resources/bundled-skills/conversation-to-skill/SKILL.md · 429 lines

How it starts

The opening of the file, as written. The whole thing — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conversation To Skill

This skill turns the work happening in the current conversation into a reusable agent skill.

Its job is not just to write SKILL.md. Its job is to identify the durable workflow, separate it from one-off thread noise, decide the right packaging and placement, and produce a skill that will actually help a future agent perform better.

When useful, this skill should borrow the practical methods of skill-creator: good descriptions, clean skill structure, eval-friendly organization, and an improve-via-feedback loop. When this skill owns evaluation, bundle the relevant toolchain locally under agents/, assets/, eval-viewer/, scripts/, and references/ so it stays self-contained instead of depending on another skill directory at runtime.

Use This Skill For

Use this skill when the user is trying to:

  • turn the current task or workflow into a reusable skill
  • capture a successful collaboration pattern for future runs
  • standardize how a class of tasks should be handled
  • extract a repeatable agent workflow from the current thread
  • package a reasoning framework, execution sequence, or artifact pattern into a skill
  • upgrade an existing draft skill so it is general, usable, and easier to trigger

Typical prompts:

  • "Turn what we're doing into a skill."
  • "I want this conversation to become an agent capability."
  • "Make this reusable for next time."
  • "Abstract this workflow into a Codex skill."
  • "This should be a standard operating pattern, not a one-off chat."
  • "Clean up this skill and make it actually reusable."

Do Not Use This Skill For

Do not use this skill when the user mainly wants:

  • a summary of the conversation without creating a reusable skill
  • immediate execution of the task with no abstraction step
  • a skill generated from multiple unseen threads you cannot inspect
  • a rigid template that blindly copies file paths, project names, or temporary constraints
  • a generic skill factory that ignores what was actually valuable in the conversation

Read the full file on GitHub · 429 lines

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 · 429 lines · 113 tokens per session scan A fea3099194a9

Subscribe to this mod's changes

conversation-to-skill is a skill published in the GitHub repository Undertone0809/rudder (288 stars, last pushed yesterday), licensed Apache-2.0. It adds 113 tokens to every session and 3,057 once invoked, about $0.0006 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens