docs

docs is a skill for Claude Code, Codex from rekabytes/opencode-skills. It costs 7 tokens per session (1,615 once invoked), scanned A, original, MIT.

Guidance for writing project documentation, including README files, API references, and code comments. An API reference explains how software endpoints accept data and return results.

In plain words
What is it for?
Use it to create or improve README files, document API endpoints, and add clear comments to code.
Why use it?
It provides a consistent structure so developers can understand, install, use, and contribute to a project.

Skill for Claude CodeCodex

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

Good fit Use it to create or improve README files, document API endpoints, and add clear comments to code.

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

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 docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/rekabytes/opencode-skills/docs/github.svg)](https://agentmods.dev/skills/rekabytes/opencode-skills/docs)
Your own site
<a href="https://agentmods.dev/skills/rekabytes/opencode-skills/docs"><img src="https://agentmods.dev/badge/skills/rekabytes/opencode-skills/docs/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.

agentmods 80×15 button for docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/rekabytes/opencode-skills/docs"><img src="https://agentmods.dev/badge/skills/rekabytes/opencode-skills/docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,615 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.00007 $0.01615
Opus 5.5 $0.00003 $0.00646
Sonnet 5.5 $0.00001 $0.00323
Haiku 4.5 $0.00001 $0.00161

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

Security

Grade A, and why

docs 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 2mo 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.

templates/skills/docs/SKILL.md · 303 lines

How it starts

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

Documentation Standards

1. README Structure

Essential Sections

# Project Name
Brief description (1-2 sentences)

## Features
- Key feature 1
- Key feature 2

## Quick Start
### Installation
### Basic Usage

## Documentation
Link to full docs

## Contributing
How to contribute

## License
MIT / etc.

Optional Sections

  • Screenshots/Demo
  • Prerequisites
  • Configuration
  • Examples
  • FAQ
  • Changelog

2. API Documentation

Endpoint Format

## Endpoint Name

`METHOD /path/to/endpoint`

Brief description of what it does.

### Parameters

| Name | Type | Required | Description |
|------|------|----------|-------------|
| id | string | Yes | Resource identifier |

### Request
```json
{
  "field": "value"
}

Response

{
  "success": true,
  "data": {}
}

Errors

Code Description
400 Invalid input
401 Unauthorized

## 3. Code Comments

### JSDoc/TSDoc Format
```typescript
/**
 * Brief description of the function.
 * 
 * @param paramName - Description of parameter
 * @returns Description of return value
 * @throws {ErrorType} When this happens
 * @example
 * ```ts
 * const result = functionName('value')
 * ```
 */
function functionName(paramName: string): ReturnType {
  // implementation
}

When to Comment

  • Complex algorithms
  • Non-obvious decisions
  • Workarounds and hacks
  • Public APIs
  • Gotchas and edge cases

When NOT to Comment

  • Self-explanatory code
  • What the code does (focus on why)
  • Redundant type information
  • Obvious operations

4. Tutorial Structure

Sections

  1. Overview - What you'll learn
  2. Prerequisites - What you need
  3. Step-by-step guide - Numbered steps
  4. Complete example - Full working code
  5. Next steps - Where to go from here

Writing Tips

  • One concept per step
  • Show, don't just tell
  • Anticipate errors
  • Provide checkpoints
  • Link to references

5. Architecture Documentation

System Overview

# Architecture

## High-Level Design
Diagram or description of main components

## Components
### Component A
- Responsibility
- Dependencies
- Key interfaces

## Data Flow
How data moves through the system

## Key Decisions
### Decision 1
- Context
- Options considered
- Chosen solution
- Rationale

Read the full file on GitHub · 303 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. 2mo ago First seen · 303 lines · 7 tokens per session scan A e7f353c21cb6

Subscribe to this mod's changes

docs is a skill published in the GitHub repository rekabytes/opencode-skills (5 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 1,615 once invoked, about $0.0000 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-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens