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/archimedes-run/omniharness/code-documentationnpx skills add archimedes-run/omniHarness --skill code-documentationgit clone --depth 1 https://github.com/archimedes-run/omniHarnessWhat 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.00088 | $0.03076 |
| Opus 5 | $0.00044 | $0.01538 |
| Sonnet 5 | $0.00018 | $0.00615 |
| Haiku 4.5 | $0.00009 | $0.00308 |
Grade A, and why
code-documentation 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 2d 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.
This is a copy
100% identical to code-documentation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Documentation Skill
Overview
This skill generates professional, comprehensive documentation for software projects, codebases, libraries, and APIs. It follows industry best practices from projects like React, Django, Stripe, and Kubernetes to produce documentation that is accurate, well-structured, and useful for both new contributors and experienced developers.
The output ranges from single-file READMEs to multi-document developer guides, always matched to the project's complexity and the user's needs.
Core Capabilities
- Generate comprehensive README.md files with badges, installation, usage, and API reference
- Create API reference documentation from source code analysis
- Produce architecture and design documentation with diagrams
- Write developer onboarding and contribution guides
- Generate changelogs from commit history or release notes
- Create inline code documentation following language-specific conventions
- Support JSDoc, docstrings, GoDoc, Javadoc, and Rustdoc formats
- Adapt documentation style to the project's language and ecosystem
When to Use This Skill
Always load this skill when:
- User asks to "document", "create docs", or "write documentation" for any code
- User requests a README, API reference, or developer guide
- User shares a codebase or repository and wants documentation generated
- User asks to improve or update existing documentation
- User needs architecture documentation, including diagrams
- User requests a changelog or migration guide
Documentation Workflow
Phase 1: Codebase Analysis
Before writing any documentation, thoroughly understand the codebase.
Step 1.1: Project Discovery
Identify the project fundamentals:
| Field | How to Determine |
|---|---|
| Language(s) | Check file extensions, package.json, pyproject.toml, go.mod, Cargo.toml, etc. |
| Framework | Look at dependencies for known frameworks (React, Django, Express, Spring, etc.) |
| Build System | Check for Makefile, CMakeLists.txt, webpack.config.js, build.gradle, etc. |
| Package Manager | npm/yarn/pnpm, pip/uv/poetry, cargo, go modules, etc. |
| Project Structure | Map out the directory tree to understand the architecture |
| Entry Points | Find main files, CLI entry points, exported modules |
| Existing Docs | Check for existing README, docs/, wiki, or inline documentation |
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.
- 2d ago First seen · 416 lines · 88 tokens per session scan A 75721d7bc1b2
code-documentation is a skill published in the GitHub repository archimedes-run/omniHarness (6 stars, last pushed 7d ago), licensed MIT. It adds 88 tokens to every session and 3,076 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-documentation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
debugging-output-and-previewing-html-using-ray
Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.
fortify-development
ACTIVATE when the user works on authentication in Laravel. This includes login, registration, password reset, email verification, two-factor authentication (2FA/TOTP/QR codes/recovery codes), passkeys, profile updates, password confirmation, or any auth-related routes and controllers. Activate when the user mentions…
timeboxed-iterating
Use when the user specifies a task and a duration, and the work should be done iteratively by subagents over that time period.
project-snmp-profiles-authoring
Use when editing Netdata SNMP profile YAMLs, topology SNMP profiles, ddsnmp profile parsing, or profile-format documentation. Requires checking source MIB field accessibility, especially MAX-ACCESS not-accessible INDEX objects, before adding or changing profile symbols.
learn-pr-preview
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge. Do not trigger for ordinary docs edits unless the user asks for a local Learn preview.
add-custom-domain
Add a custom domain to a Temps project and provision an automatic SSL/TLS certificate via Let's Encrypt, driven entirely from the @temps-sdk/cli CLI. Handles subdomains, apex domains, HTTP-01 and DNS-01 challenges, and wildcard domains. Use when the user wants to: (1) Add a custom domain to their Temps app, (2) Set up…