Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JeremyDev87/codingbuddynpx agentmods add skills/jeremydev87/codingbuddy/documentation-generationWrote 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.
[](https://agentmods.dev/skills/jeremydev87/codingbuddy/documentation-generation)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/documentation-generation"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/documentation-generation/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.
<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/documentation-generation"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/documentation-generation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.01590 |
| Opus 5.5 | $0.00012 | $0.00636 |
| Sonnet 5.5 | $0.00006 | $0.00318 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade C, and why
documentation-generation scanned grade C with 1 finding 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 1mo 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
// Extract environment variables How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Generation
Overview
Good documentation is the gift you give your future self and your team. It is NOT optional.
Core principle: Documentation describes behavior, not code. If the code changes, update the docs.
Iron Law:
DOCS ARE OUTDATED THE MOMENT THEY ARE WRITTEN — AUTOMATE OR ACCEPT THE DEBT
When to Use
- Creating a new project README
- Documenting new API endpoints
- Generating CHANGELOG entries
- Writing architecture decision records (ADRs)
- Creating onboarding guides for new team members
- Documenting AI rules for multi-tool projects
Document Types & Templates
1. README.md
A good README answers: What is this? How do I run it? How do I use it?
# Project Name
One-sentence description of what this does and who it's for.
## Quick Start
\`\`\`bash
npm install
npm run dev
\`\`\`
## Features
- Feature 1: Brief description
- Feature 2: Brief description
## Installation
\`\`\`bash
# Prerequisites
node >= 18
npm >= 9
# Install
npm install
# Configure
cp .env.example .env
# Edit .env with your values
# Run
npm start
\`\`\`
## Configuration
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `PORT` | No | `3000` | Server port |
| `DATABASE_URL` | Yes | — | PostgreSQL connection string |
## API Reference
See [API Documentation](./docs/api.md) for full reference.
## Contributing
See [CONTRIBUTING.md](./CONTRIBUTING.md).
## License
MIT
2. API Documentation
# API Reference
## Authentication
All endpoints require Bearer token:
\`\`\`
Authorization: Bearer <token>
\`\`\`
## Endpoints
### GET /users
List all users.
**Parameters:**
| Name | Type | Required | Description |
|------|------|----------|-------------|
| `page` | integer | No | Page number (default: 1) |
| `limit` | integer | No | Per-page count (default: 20, max: 100) |
**Response:**
\`\`\`json
{
"data": [{ "id": "123", "email": "[email protected]" }],
"meta": { "total": 42, "page": 1 }
}
\`\`\`
**Errors:**
| Code | Status | Description |
|------|--------|-------------|
| `UNAUTHORIZED` | 401 | Missing or invalid token |
| `FORBIDDEN` | 403 | Insufficient permissions |
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.
- 1mo ago First seen · 294 lines · 31 tokens per session scan C 81199a874023
documentation-generation is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 1,590 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
ring:planning-codebase-simplification
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…