authoring-a-skill

authoring-a-skill is a skill for Claude Code, Codex from New1Direction/korgex. It costs 25 tokens per session (331 once invoked), scanned A, original, MIT.

A reusable instruction file for teaching an AI coding agent how to handle a recurring kind of work. It stores the procedure, order of steps, and checks in a SKILL.md file.

In plain words
What is it for?
Use it to create project-specific or global skills for repeatable tasks. It helps define when the agent should use a skill and what steps it should follow.
Why use it?
It prevents the agent from having to rediscover the same process each time. It also separates general procedures from one-off project notes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it to create project-specific or global skills for repeatable tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/new1direction/korgex/authoring-a-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 New1Direction/korgex --skill authoring-a-skill
Clone the repo
git clone --depth 1 https://github.com/New1Direction/korgex

Made for: Claude Code, 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 authoring-a-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/new1direction/korgex/authoring-a-skill.svg)](https://agentmods.dev/skills/new1direction/korgex/authoring-a-skill)
Your own site
<a href="https://agentmods.dev/skills/new1direction/korgex/authoring-a-skill"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/authoring-a-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 331 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 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.00025 $0.00331
Opus 5 $0.00013 $0.00166
Sonnet 5 $0.00005 $0.00066
Haiku 4.5 $0.00003 $0.00033

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

Security

Grade A, and why

authoring-a-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 7d 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.

src/skills_builtin/authoring-a-skill/SKILL.md · 30 lines

What it actually says

A skill captures a durable, repeatable procedure so it doesn't have to be re-derived. Write one when you've solved something you'll plausibly hit again.

  1. Is it skill-worthy? Yes if it's a GENERAL, reusable procedure. No if it's a one-off answer or project-specific trivia (that belongs in memory/AGENTS.md).
  2. Location & format. Create ./.korgex/skills/<kebab-name>/SKILL.md (project) or ~/.korgex/skills/<kebab-name>/SKILL.md (global). Frontmatter:
    ---
    name: <kebab-name>
    description: <one line — used to decide when to load it>
    version: 1.0
    trust: user
    ---
    
  3. Write the body as a short numbered procedure: the steps to follow, the order, and the checks. Keep it tight — it's injected by description and loaded on demand, so the body should be actionable, not an essay.
  4. Scope the name well. The description is the only thing the agent sees when deciding to use it, so make it specific and trigger-able.
  5. Leave trust: user. korgex's own learned skills are trust: agent; never hand-edit a built-in.
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. 7d ago First seen · 30 lines · 25 tokens per session scan A 392a9252b98d

Subscribe to this mod's changes

authoring-a-skill is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 331 once invoked, about $0.0001 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.

Related

Other skills, from other repositories