in-progress

in-progress is a skill for Claude Code, Codex from ntaffzii/Skill-Agents. It costs 42 tokens per session (479 once invoked), scanned A, original, MIT.

A staging process for draft agent skills that are still being tested and are not ready for general use.

In plain words
What is it for?
Use it to define a small experiment, test realistic prompts, check prompts that should not trigger it, and decide whether to promote or retire the draft.
Why use it?
It prevents unfinished skills from being treated as stable while their purpose, trigger, scope, and workflow are still uncertain.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/ntaffzii/skill-agents/in-progress
Any agent
npx skills add ntaffzii/Skill-Agents --skill in-progress
Clone the repo
git clone --depth 1 https://github.com/ntaffzii/Skill-Agents

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 in-progress

README.md
[![agentmods](https://agentmods.dev/badge/skills/ntaffzii/skill-agents/in-progress.svg)](https://agentmods.dev/skills/ntaffzii/skill-agents/in-progress)
Your own site
<a href="https://agentmods.dev/skills/ntaffzii/skill-agents/in-progress"><img src="https://agentmods.dev/badge/skills/ntaffzii/skill-agents/in-progress.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 479 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00042 $0.00479
Opus 5 $0.00021 $0.00239
Sonnet 5 $0.00008 $0.00096
Haiku 4.5 $0.00004 $0.00048

Measured 4d ago against content hash 695ce6ee92f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

in-progress 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 4d 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.

skills/in-progress/SKILL.md · 65 lines

How it starts

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

In Progress Skill Incubator

Use this skill for draft skills that need iteration before becoming public or team-ready.

Purpose

skills/in-progress/ is a staging area. A draft belongs here when the idea is useful but the trigger, workflow, scope, or validation is still uncertain.

Rules

  • Draft skills should not be listed as stable skills in the root README.
  • Keep experiments small enough to promote or retire quickly.
  • Do not add large references until the core workflow works.
  • Do not promote a skill without realistic trigger examples.

Workflow

  1. Define the experiment

    • State the repeated task the draft skill should improve.
    • Name the expected trigger phrases.
    • Identify what the agent should do differently after loading it.
  2. Draft narrowly

    • Give the skill one main job.
    • Prefer workflow steps over broad advice.
    • Add stop conditions when misuse is likely.
  3. Test with realistic prompts

    • Try at least three prompts that should trigger the skill.
    • Try one prompt that should not trigger it.
    • Note where the instructions are too vague or too broad.
  4. Decide status

    • Promote to a domain bucket when the workflow is stable and useful.
    • Keep in progress when examples still fail or scope is unclear.
    • Move to deprecated/ when the idea is no longer worth pursuing.
  5. Promote cleanly

    • Move the skill folder into the right bucket.
    • Update README references if the skill is public.
    • Update workflows or registries only when the skill is part of a repeatable job.

Promotion Checklist

  • name is lowercase and hyphenated.
  • description clearly says when to use the skill.
  • The body has a workflow, rules, and verification or output guidance.
  • The skill has one main job.
  • It does not duplicate another stable skill.
  • Any long examples or references are moved into references/.

Output Format

End with:

  • Draft status
  • What changed
  • What still needs testing
  • Promote, keep, or retire recommendation

Read the full file on GitHub · 65 lines

Files

What ships with it

1 file 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.

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. 4d ago First seen · 65 lines · 42 tokens per session scan A 695ce6ee92f6

Subscribe to this mod's changes

in-progress is a skill published in the GitHub repository ntaffzii/Skill-Agents (4 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 479 once invoked, about $0.0002 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

bugs

Proactively sweep a Pake area for latent UX and runtime defects before users report them, using this repo's own fix history and boundary archetypes, and confirm every finding with a probe run this turn. Use for 找找有没有bug, 主动找bug, 有没有隐患, 排查隐患, 举一反三, 上线前扫一遍, 这块可靠吗, latent bug scan, sibling sweep after a fix. Not for an…

tw93/Pake · 0 tokens

ux-audit

Audit a page / surface against the Designing Interfaces pattern language + the ux skill checklists, then land findings. Three layers — static (code), visual (screenshots), dynamic (automated user journey + perf). Use to run a repeatable, standards-based UX review of one screen.

lobehub/lobehub · 62 tokens

ux

LobeHub product design values / principles / checklists. Use whenever the work touches user-interface features or implementation — designing or building any user-facing flow — to get better UX results.

lobehub/lobehub · 39 tokens

design-prototype

Produce an interactive single-file HTML design prototype using the REAL LobeHub design system (@lobehub/ui + antd + antd-style tokens) with production-style React — no build step, opens directly in a browser. Use when asked for a design prototype / interactive mockup / 交互原型 / 出个原型 / 设计稿 HTML for a page or flow, or to…

lobehub/lobehub · 92 tokens

bootstrap

Bootstrap CSS framework for responsive design. Use for quick styling.

G1Joshi/Agent-Skills · 14 tokens

chakraui

Chakra UI accessible React components. Use for React UI.

G1Joshi/Agent-Skills · 16 tokens