nw-agent-creation-workflow

nw-agent-creation-workflow is a skill for Claude Code from nWave-ai/nWave. It costs 24 tokens per session (1,700 once invoked), scanned A, original, MIT.

A five-phase process for creating coding agents: analyse, design, create, validate, and refine. It defines the purpose, inputs, outputs, and quality checks for each phase.

In plain words
What is it for?
Use it to plan an agent, choose whether it is a specialist, reviewer, or coordinator, select its tools and skills, test its behaviour, and revise it.
Why use it?
It helps prevent agents from having unclear responsibilities, duplicated work, or unnecessary tools. Validation and refinement provide a way to improve an agent based on observed failures.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Good fit Use it to plan an agent, choose whether it is a specialist, reviewer, or coordinator, select its tools and skills, test its behaviour, and revise it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nwave-ai/nwave/nw-agent-creation-workflow
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 nWave-ai/nWave --skill nw-agent-creation-workflow
Clone the repo
git clone --depth 1 https://github.com/nWave-ai/nWave

Made for: Claude Code.

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 nw-agent-creation-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-agent-creation-workflow.svg)](https://agentmods.dev/skills/nwave-ai/nwave/nw-agent-creation-workflow)
Your own site
<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-agent-creation-workflow"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-agent-creation-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,700 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 52
    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 Agent Snooping · line 103
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00024 $0.01700
Opus 5 $0.00012 $0.00850
Sonnet 5 $0.00005 $0.00340
Haiku 4.5 $0.00002 $0.00170

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

Security

Grade A, and why

nw-agent-creation-workflow 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 8d 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.

nWave/skills/nw-agent-creation-workflow/SKILL.md · 176 lines

How it starts

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

Agent Creation Workflow

Overview

Create agents through 5 phases: ANALYZE -> DESIGN -> CREATE -> VALIDATE -> REFINE. Each phase has clear inputs, outputs, and quality gates. Follow "start minimal, add based on failure."

Phase 1: ANALYZE

Goal: Understand requirements and determine agent architecture.

Inputs: User requirements, use case description, existing codebase context.

Steps:

  1. Identify single clear responsibility
  2. Determine new agent or modification of existing
  3. Check overlap with existing agents (avoid duplication)
  4. Classify agent type:
    • Specialist: Single-domain expert (most common)
    • Reviewer: Validates outputs from another agent (Reflection pattern)
    • Orchestrator: Coordinates multiple agents
  5. Identify required tools (start with Read, Glob, Grep -- add only what's needed)
  6. Determine if Skills needed (domain knowledge > 50 lines)

Gate: Single responsibility identified. Agent type classified. No overlap.

Output: Requirements summary with agent type, tools list, skill needs.

Phase 2: DESIGN

Goal: Design agent architecture and structure.

Inputs: Requirements summary from Phase 1.

Steps:

  1. Select design pattern (load design-patterns skill)
  2. Define role and goal (1-2 sentences each)
  3. Identify core principles that DIVERGE from Claude defaults:
    • What must this agent do differently than Claude naturally would?
    • Domain-specific methodology steps
    • Non-obvious constraints | Project-specific conventions
  4. Design workflow (3-7 phases)
  5. Plan Skills extraction: domain knowledge -> separate Skill | Testing/validation -> separate Skill | Keep workflow and principles in core agent
  6. Design Skill Loading Strategy (required for 3+ skills):
    • Map each skill to the workflow phase where it's needed
    • Create a loading table: Phase → Skill → Trigger condition
    • Add explicit Load: skill-name directives in each workflow phase
    • Document path: ~/.claude/skills/nw-{skill-name}/SKILL.md (installed) or nWave/skills/nw-{skill-name}/SKILL.md (repo)
    • Note: skills: in frontmatter is declarative only — Claude Code does NOT auto-load skill files. The agent must use Read tool to load them, triggered by Load: directives in workflow text.
  7. Draft frontmatter:
    ---
    name: {kebab-case-id}
    description: Use for {domain}. {When to delegate.}
    model: inherit
    tools: [{minimum tools needed}]
    maxTurns: 30
    skills:
      - nw-{skill-name}
    ---
    

Read the full file on GitHub · 176 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. 8d ago First seen · 176 lines · 24 tokens per session scan A 98a9ef586280

Subscribe to this mod's changes

nw-agent-creation-workflow is a skill published in the GitHub repository nWave-ai/nWave (608 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,700 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-30.