doc-master

A documentation toolkit with separate helpers for writing software documentation for areas such as APIs, databases, tests, architecture, and user guides.

In plain words
What is it for?
Creating or improving backend, frontend, API, database, architecture, test, user-guide, compliance, and mobile documentation.
Why use it?
It organizes documentation work by subject, making it easier to cover the different parts of a software project.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add hculap/better-code
agentmods
npx agentmods add plugins/hculap/better-code/doc-master
Clone the repo
git clone --depth 1 https://github.com/hculap/better-code

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

doc-master 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.

plugins/doc-master/.claude-plugin/plugin.json · 30 lines

What it actually says

{
  "name": "doc-master",
  "version": "0.2.1",
  "description": "Comprehensive documentation toolkit with specialized agents for bulletproof software documentation across backend, frontend, API, database, architecture, tests, user guides, compliance, and mobile domains.",
  "author": {
    "name": "Szymon Paluch"
  },
  "repository": "https://github.com/hculap/better-code",
  "homepage": "https://github.com/hculap/better-code#readme",
  "license": "MIT",
  "keywords": [
    "documentation",
    "diataxis",
    "api-docs",
    "technical-writing",
    "software-docs"
  ],
  "agents": [
    "./agents/backend-docs.md",
    "./agents/frontend-docs.md",
    "./agents/api-docs.md",
    "./agents/database-docs.md",
    "./agents/architecture-docs.md",
    "./agents/test-docs.md",
    "./agents/user-guide-docs.md",
    "./agents/compliance-docs.md",
    "./agents/mobile-docs.md"
  ]
}
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 · 30 lines scan A 3dc28cb0c043

Subscribe to this mod's changes

doc-master is a plugin published in the GitHub repository hculap/better-code (2 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Related

Other plugins, from other repositories

claude-ops

Claude Code operations toolkit. Twelve skills: audit-skill-visibility (audit whether each installed skill is actually VISIBLE to the model, and diagnose why most of a fleet never gets used — a skill is invisible when its description is dropped by Claude Code's skill-listing context budget, which drops descriptions…

melodic-software/claude-code-plugins · not measured

context-guard

Per-session context-window observability plus the first shipped consumer: a statusline wrapper tees each session's contextwindow fields to a per-session snapshot file, a zone resolver classifies usage into smart/acceptable/dumb bands (percentage bands plus window-class token bands, conservative-min combination, zones.

melodic-software/claude-code-plugins · not measured

ai-briefing

Build source-backed AI-industry briefings from official vendor publications, configured RSS/Atom feeds, GitHub releases, reputable secondary reporting, and user-supplied URLs. Deduplicate, rank, and present results as markdown or optional HTML/PPTX decks, with repository-owned profile, audience, and brand…

melodic-software/claude-code-plugins · not measured

context-budget

Measure a Claude Code session's fixed startup context payload per item, on the consumer's machine at a pinned, version-stamped binary — including per-tool attribution of the built-in tool pools that /context reports only as lump sums, derived live by A/B bare-name-deny differencing with enforced comparability rules…

melodic-software/claude-code-plugins · not measured

bugs

Produces a structured five-field bug report — title, steps to reproduce, expected vs actual, severity with justification, and suggested fix location — from an informal defect description. Read-only by default: it emits the report and never edits code, opens a PR, or files an issue on its own.

melodic-software/claude-code-plugins · not measured

claude-memory

Keeps a repo's Claude Code memory layer healthy and under your control, against criteria derived from official Claude Code documentation. The audit skill checks the instruction/memory layer (CLAUDE.md, CLAUDE.local.md, .claude/rules/, auto-memory) with a deterministic script-backed spine plus judgment-tier checks. The.

melodic-software/claude-code-plugins · not measured