PixelPilot api-documentation.instructions.md

A code-documentation tool that reads a file or folder and creates Markdown documentation such as a README, API reference, code annotations, or a text-based architecture diagram.

In plain words
What is it for?
Use it to document code, generate a README, write an API reference, add JSDoc or TSDoc comments, or explain a project’s architecture.
Why use it?
It removes the need to manually inspect source code and describe its functions, inputs, outputs, side effects, and errors.

Instructions file for GitHub Copilot

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.

agentmods
npx agentmods add instructions/dev-lou/pixelpilot/api-documentation
Clone the repo
git clone --depth 1 https://github.com/dev-lou/PixelPilot

Made for: GitHub Copilot.

Per session 2,164 This file is loaded in full into every session.
When invoked 2,164 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.02164 $0.02164
Opus 5 $0.01082 $0.01082
Sonnet 5 $0.00433 $0.00433
Haiku 4.5 $0.00216 $0.00216

Measured yesterday against content hash 8a6f70968091, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

PixelPilot api-documentation.instructions.md 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.

vscode/.github/instructions/api-documentation.instructions.md · 343 lines

How it starts

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

API Documentation 2026

Analyse code → extract contracts → generate docs → output structured markdown. Produces README, API reference, JSDoc/TSDoc annotations, and architecture diagrams from source files without requiring external tools.


TRIGGER

This skill is activated by:

  • /doc [file-or-directory] command
  • "document this", "generate docs", "write a README", "API reference for…"
  • "explain the architecture of…"

STEP 1 — ANALYSE THE TARGET

For a single file

// Read and parse the file
const source = await read_file(targetPath);

// Extract:
// 1. Exported functions/classes/types
// 2. Function signatures (name, params, return type)
// 3. Existing JSDoc/TSDoc comments
// 4. Side effects (DB calls, API calls, mutations)
// 5. Error conditions (thrown errors, rejected promises)

For a directory

# Get the file tree first
find ./src -name "*.ts" -o -name "*.tsx" -o -name "*.js" | sort

# Read key files: index files first, then by depth
# index.ts / index.js → exports → implementation files

STEP 2 — CHOOSE DOCUMENTATION TYPE

Requested Output format
"README" README.md with overview, install, usage, examples
"API reference" Per-function/class markdown reference
"Architecture diagram" Mermaid diagram + text description
"JSDoc / TSDoc" Inline annotations added to source
"/doc" (unspecified) README + API reference

STEP 3A — README GENERATION

<!-- Template: README.md -->
# {Package / Component Name}

> {One-sentence description of what it does and why it exists.}

## Installation

```bash
npm install {package}
# or
pnpm add {package}

Quick Start

import { {MainExport} } from '{package}';

// Minimal working example
const result = await {MainExport}({
  {requiredParam}: 'value',
});
console.log(result);

Usage

{Use case 1}

// Annotated example with context

{Use case 2}

// …

API Reference

See API.md for the full reference.

Function Description
{name}(params) {one-line description}

Configuration

Option Type Default Description
{option} {type} {default} {description}

Error Handling

try {
  await {MainExport}(params);
} catch (err) {
  if (err instanceof {SpecificError}) {
    // handle …
  }
}

Browser / Node Compatibility

{Table or list of supported environments}

Changelog

See CHANGELOG.md.

License

{LICENSE}

Read the full file on GitHub · 343 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. yesterday First seen · 343 lines · 2,164 tokens per session scan A 8a6f70968091

Subscribe to this mod's changes

PixelPilot api-documentation.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 4mo ago), licensed MIT. It adds 2,164 tokens to every session, about $0.0108 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.