What is ak-dev-write-spec?

A staged documentation process for planning a change to Agent Kernel, a software project. It produces a design document, a detailed implementation specification, and an implementation plan in that order.

Use it to create planning documents under docs/specs/ before implementing an Agent Kernel issue. The design is reviewed first, followed by the detailed specification and then the step-by-step plan.

It separates human review of the proposed design from detailed technical planning. This prevents extensive implementation details from being written for a design that may later change.

How yaalalabs/agent-kernel configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to yaalalabs/agent-kernel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/yaalalabs/agent-kernel/develop/.agents/skills/ak-dev-write-spec/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/yaalalabs/agent-kernel

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yaalalabs/agent-kernel/ak-dev-write-spec/github.svg)](https://agentmods.dev/skills/yaalalabs/agent-kernel/ak-dev-write-spec)

Your own site

<a href="https://agentmods.dev/skills/yaalalabs/agent-kernel/ak-dev-write-spec"><img src="https://agentmods.dev/badge/skills/yaalalabs/agent-kernel/ak-dev-write-spec/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yaalalabs/agent-kernel/ak-dev-write-spec"><img src="https://agentmods.dev/badge/skills/yaalalabs/agent-kernel/ak-dev-write-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 143 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,217 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 pass 7 Sept 2026

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.

Model	Per session	Once invoked
Fable 5.1	$0.00143	$0.06217
Opus 5.5	$0.00057	$0.02487
Sonnet 5.5	$0.00029	$0.01243
Haiku 4.5	$0.00014	$0.00622

Measured 1mo ago against content hash 8062ac961209, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ak-dev-write-spec 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 1mo 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.

.agents/skills/ak-dev-write-spec/SKILL.md · 335 lines

How it starts

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

Write a Spec for a Planned Change

Use this skill when asked to produce spec documents for Agent Kernel work before (or instead of) implementing it. A change is specified in three documents, written in strict order, all under docs/specs/<issue-number>-<short-title>/:

Stage	File	What it is	Written when
1	`design.md`	Concise, point-form, hierarchical requirements — what changes and why	First, before anything else
2	`spec.md`	Detailed design and implementation components, following the approved design	Only after `design.md` has been reviewed and optimized through review cycles
3	`plan.md`	Concise breakdown of the implementation into iterations/steps	Only after both `design.md` and `spec.md` are done

Do not skip ahead. design.md is the document humans review — it must exist and survive its review cycles before effort goes into spec.md. Writing a detailed spec against an unreviewed design wastes the detail work when the design changes.

The same directory may optionally hold a research/ subfolder — the supporting investigation that informed the design (provider surveys, prior-art comparisons, benchmarks, spike notes). It is not a fourth stage and not required; see Optional: research/.

This skill is for writing these documents, not for implementing the change they describe.

Which Stage Are You In?

Route from what the requester asked for and what already exists in docs/specs/<issue-number>-<short-title>/:

No design.md yet, or the request is "write a spec/design for X" → Stage 1: write design.md and stop there.
design.md exists and the requester says it is reviewed/approved (or asks for the implementation spec) → Stage 2: write spec.md.
design.md and spec.md both exist and the requester asks for the plan/breakdown → Stage 3: write plan.md.
Asked to update an existing document → update that document; if the update changes requirements in design.md, flag that downstream spec.md/plan.md need re-alignment.
Asked to capture or record research — a provider survey, a prior-art comparison, a benchmark, a spike — → write it under research/ (optional; see Optional: research/). This can happen before design.md exists and does not, on its own, start Stage 1.

Read the full file on GitHub · 335 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.

1mo ago Changed · +19 lines 8062ac961209
2mo ago First seen · 316 lines · 143 tokens per session scan A 483dadb3ddc1

Subscribe to this mod's changes

ak-dev-write-spec is a skill published in the GitHub repository yaalalabs/agent-kernel (192 stars, last pushed yesterday), licensed Apache-2.0. It adds 143 tokens to every session and 6,217 once invoked, about $0.0006 per session on Opus 5.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.

Planning Writing and docs a2a adk ai-agents aws azure cloud-native

ak-dev-write-spec next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ak-dev-write-specyaalalabs/agent-kernel	Skill	192	yesterday	Apache-2.0	A	143	Claude Code, Codex
cloud-native-security-defensivej4flmao/agent-skills	Skill	38	3d ago	MIT	A	127	Claude Code, Codex
notionArvo-AI/aurora	Skill	454	yesterday	Apache-2.0	A	23	Claude Code
datadogArvo-AI/aurora	Skill	454	yesterday	Apache-2.0	A	28	Claude Code
scalewayArvo-AI/aurora	Skill	454	yesterday	Apache-2.0	A	29	Claude Code
terrasharkLukasNiessen/terrashark	Skill	710	4d ago	MIT	A	56	Claude Code, Codex
isaac-automatorisaac-sim/IsaacAutomator	Skill	270	11d ago	Apache-2.0	A	123	Claude Code, Codex

agent-kernel: Skill for Claude Code