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.
npx agentmods add skills/rekabytes/opencode-skills/docsnpx skills add rekabytes/opencode-skills --skill docsgit clone --depth 1 https://github.com/rekabytes/opencode-skillsWhat 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 | $0.00007 | $0.01615 |
| Opus 5 | $0.00003 | $0.00807 |
| Sonnet 5 | $0.00001 | $0.00323 |
| Haiku 4.5 | $0.00001 | $0.00161 |
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 yesterday.
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.
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
- Overview - What you'll learn
- Prerequisites - What you need
- Step-by-step guide - Numbered steps
- Complete example - Full working code
- 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
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.
- yesterday First seen · 303 lines · 7 tokens per session scan A e7f353c21cb6
docs is a skill published in the GitHub repository rekabytes/opencode-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 1,615 once invoked, about $0.0000 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…