dorkos: Skill for Claude Code

.agents/skills/writing-developer-guides/SKILL.md

writing-developer-guides is a skill for Claude Code from dork-labs/dorkos. It costs 36 tokens per session (1,167 once invoked), scanned A, original, MIT.

A guide-writing skill for documentation aimed at both developers and coding agents. It explains how to organize developer guides so important information is easy to find.

In plain words
What is it for?
Use it when creating, updating, or reviewing guides in a project’s contributing documentation.
Why use it?
It removes the guesswork from deciding what a project guide should contain and how it should be structured.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

This is dork-labs/dorkos's own configuration. It tells Claude Code how to work on dorkos itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dorkos configures →

Part of the flow plugin — 31 skills, 39 commands, 5 agents, 4 hooks shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to dork-labs/dorkos. 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/dork-labs/dorkos/main/.agents/skills/writing-developer-guides/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 31 skills, 39 commands, 5 agents, 4 hooks.

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 writing-developer-guides

README.md
[![agentmods](https://agentmods.dev/badge/skills/dork-labs/dorkos/writing-developer-guides.svg)](https://agentmods.dev/skills/dork-labs/dorkos/writing-developer-guides)
Your own site
<a href="https://agentmods.dev/skills/dork-labs/dorkos/writing-developer-guides"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/writing-developer-guides.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,167 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01167
Opus 5 $0.00018 $0.00583
Sonnet 5 $0.00007 $0.00233
Haiku 4.5 $0.00004 $0.00117

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

Security

Grade A, and why

writing-developer-guides 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.

.agents/skills/writing-developer-guides/SKILL.md · 200 lines

How it starts

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

Writing Developer Guides

Overview

This skill teaches how to write developer guides that work well for both AI coding agents and human developers. The key insight: AI agents need fast context retrieval, clear decision support, and copy-paste ready patterns.

When to Apply

  • Creating a new file in contributing/
  • Updating or refactoring an existing guide
  • Reviewing guides for completeness
  • User asks about documentation structure

Core Principle

Structure for retrieval, not teaching.

Traditional documentation assumes sequential reading. AI agents retrieve specific information based on task context. Every section should be independently useful.

Required Sections (In Order)

Each developer guide must include these sections in this sequence:

1. Title + Overview (2-3 sentences)

# [Topic] Guide

## Overview

[What this guide covers] and [why it matters for this project].

Why this order: AI agents use the overview to determine relevance before reading further.

2. Key Files Table

## Key Files

| Concept       | Location             |
| ------------- | -------------------- |
| Configuration | `src/path/config.ts` |
| Types         | `src/path/types.ts`  |

Why early: Agents need to know WHERE before HOW. This prevents searching.

3. Decision Matrix ("When to Use What")

## When to Use What

| Scenario | Approach | Why       |
| -------- | -------- | --------- |
| Need X   | Use Y    | Because Z |
| Need A   | Use B    | Because C |

Critical for AI: A good decision matrix eliminates 80% of clarifying questions. Agents can pattern-match their current task to the right approach.

4. Core Patterns (Code Examples)

## Core Patterns

### [Pattern Name]

[1-2 sentence context]

```typescript
// Complete, runnable example
// Comments explain WHY, not WHAT
export function example() {
  // This pattern ensures X because Y
  return result;
}
```

**Requirements:**
- Examples must be complete (copy-paste ready)
- Include imports if non-obvious
- Comments explain reasoning, not mechanics

### 5. Anti-Patterns

```markdown

Read the full file on GitHub · 200 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. 7d ago First seen · 200 lines · 36 tokens per session scan A 783e8e94b95b

Subscribe to this mod's changes

writing-developer-guides is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,167 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.