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/jeremydev87/codingbuddy/documentation-generationnpx skills add JeremyDev87/codingbuddy --skill documentation-generationgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWhat 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.00031 | $0.01590 |
| Opus 5 | $0.00015 | $0.00795 |
| Sonnet 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 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.
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.
- 2d 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 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,590 once invoked, about $0.0002 per session on Opus 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
om-integration-builder
Build integration provider packages for the Open Mercato Integration Marketplace (payment, shipping, data-sync, webhook). Scaffolds the npm package, adapter, credentials, widget injection, webhook processing, health checks, i18n, tests. Triggers on "build integration", "add provider", "integrate with…
om-ds-guardian
Design System Guardian for Open Mercato. Use for frontend UI work, design-system compliance reviews, semantic token migration, hardcoded color or typography cleanup, DS-compliant page scaffolding, and common DS violations such as arbitrary text sizes, raw color classes, or missing shared states. Prefer this skill…
om-integration-tests
Run and create QA integration tests (Playwright TypeScript), including executing the full suite, converting optional markdown scenarios, and generating new tests from specs or feature descriptions. Defers all environment boot/reuse to the om-prepare-test-env skill and attaches to the shared descriptor it writes. Use…
om-create-agents-md
Create or rewrite AGENTS.md files for Open Mercato packages and modules. Use this skill when adding a new package, creating a new module, or when an existing AGENTS.md needs to be created or refactored. Ensures prescriptive tone, the Always/Ask First/Never/Validation Commands boundary structure, MUST-style rules…
om-smart-test
Run only the tests affected by changed code. Use when the user says "run affected tests", "run smart tests", "test only what changed", "run tests for this PR", "run tests for my changes", "selective tests", or asks to run tests without running the full suite.
om-auto-qa-scenarios
Generate a human QA report for a window of merged PRs (date floor, PR-number floor, or default last 7 days) and ship it as a docs-only PR against develop. Groups work into P0/P1/P2 testing routes with click paths, verification points, and risk callouts. Writes markdown + HTML under .ai/analysis/. Hands off to…