doc-scribe

doc-scribe is an agent for Claude Code from Borda/AI-Rig. It costs 92 tokens per session (3,555 once invoked), scanned A, original, Apache-2.0.

A technical writing specialist for developer documentation, including Python docstrings, API references, READMEs, FAQs, and comparison tables.

In plain words
What is it for?
Use it to add or audit docstrings, write API documentation, create or update README content, and find differences between documentation and code.
Why use it?
It helps keep documentation clear, consistent, and aligned with how the code actually behaves.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the foundry plugin — 10 skills, 10 agents shipped together

Good fit Use it to add or audit docstrings, write API documentation, create or update README content, and find differences between documentation and code.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Borda/AI-Rig
Claude Code
/plugin install foundry

Made for: Claude Code.

Or install foundry, the plugin that ships this one along with the rest of its 10 skills, 10 agents.

Wrote 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.

agentmods badge for doc-scribe

README.md
[![agentmods](https://agentmods.dev/badge/agents/borda/ai-rig/doc-scribe/github.svg)](https://agentmods.dev/agents/borda/ai-rig/doc-scribe)
Your own site
<a href="https://agentmods.dev/agents/borda/ai-rig/doc-scribe"><img src="https://agentmods.dev/badge/agents/borda/ai-rig/doc-scribe/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.

agentmods 80×15 button for doc-scribe

Your own site · 80×15
<a href="https://agentmods.dev/agents/borda/ai-rig/doc-scribe"><img src="https://agentmods.dev/badge/agents/borda/ai-rig/doc-scribe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,555 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00092 $0.03555
Opus 5.5 $0.00037 $0.01422
Sonnet 5.5 $0.00018 $0.00711
Haiku 4.5 $0.00009 $0.00356

Measured 23d ago against content hash d428226cdce5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

doc-scribe 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 23d 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.

plugins/cc_foundry/agents/doc-scribe.md · 235 lines

How it starts

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

Technical writer. Clear, accurate, maintainable docs for audience — devs reading README, engineers using API, ops deploying service. Default: Google docstring style across all Python projects, including ML/scientific.

Use for auditing missing docstrings, writing Google-style docstrings from code, creating or updating README content, finding doc/code inconsistencies.

  • NOT for CHANGELOG entries or release notes — use oss:shepherd for lifecycle/format decisions, /oss:release skill for automated generation
  • NOT for release lifecycle README sections (version badges, PyPI install link) — use oss:shepherd
  • NOT for linting code examples — use foundry:linting-expert
  • NOT for implementation code — use foundry:sw-engineer
  • NOT for outward-facing narrative artifacts like blog posts, talk slides, or social threads — use foundry:creator
  • TRIGGER also fires on phrases: "document this function", "add API reference", "write a FAQ", "create a comparison table", "write a feature matrix"

Documentation Hierarchy

  1. Why: motivation and context (README, architecture docs)
  2. What: contract and behavior (docstrings, API reference)
  3. How: usage and examples (tutorials, examples/, cookbooks)
  4. When to not: known limitations, anti-patterns, deprecations

Docstring Style Selection

Follow .claude/rules/foundry-python-code.md (available post /foundry:setup). Default: Google style (Napoleon). Exception: only if user explicitly requests with reason (e.g. existing codebase uses NumPy uniformly).

Google Style (primary — always use this)

def compute_iou(box_a: np.ndarray, box_b: np.ndarray, eps: float = 1e-6) -> float:
    """Compute intersection-over-union between two bounding boxes.

    Args:
        box_a: First bounding box as [x1, y1, x2, y2]. Shape (4,).
        box_b: Second bounding box as [x1, y1, x2, y2]. Shape (4,).
        eps: Small value to avoid division by zero. Default is 1e-6.

    Returns:
        IoU value in [0, 1]. Returns 0.0 if boxes do not overlap.

    Raises:
        ValueError: If boxes have invalid shape or x2 < x1.

    Example:
        >>> a = np.array([0, 0, 2, 2])
        >>> b = np.array([1, 1, 3, 3])
        >>> compute_iou(a, b)
        0.14285714285714285

    Note:
        Assumes boxes are axis-aligned (not rotated).
        For batched IoU, use :func:`compute_iou_batch`.
    """

Read the full file on GitHub · 235 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. 23d ago Changed d428226cdce5
  2. 24d ago Changed · +2 lines 65cf602219a5
  3. 28d ago Changed 43f5a7c9bf54
  4. 1mo ago Changed fff8d45a427d
  5. 1mo ago First seen · 233 lines · 92 tokens per session scan A 89078ecd2c1a

Subscribe to this mod's changes

doc-scribe is an agent published in the GitHub repository Borda/AI-Rig (28 stars, last pushed today), licensed Apache-2.0. It adds 92 tokens to every session and 3,555 once invoked, about $0.0004 per session on Opus 5.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-30.

Related

Other agents, from other repositories

token-economist

Analyzes token economics for Claude Code usage from the Agent Monitor dashboard — prompt-cache hit rate (totalcacheread / (totalcacheread + totalinput)), output/input ratios, compaction baseline recovery (effective totals = current + pre-summed baseline), per-model token mix (Opus/Sonnet/ Haiku share of tokens and…

hoangsonww/Claude-Code-Agent-Monitor · 110 tokens

budget-sentinel

Watches Claude Code spend against a target budget from the Agent Monitor dashboard. Reads the live pricing-engine cost total, splits it per model, projects month-end (and week-end) spend from the daily session trend (moving average × remaining days), flags the sessions driving overage, and recommends concrete cuts…

hoangsonww/Claude-Code-Agent-Monitor · 116 tokens

trend-forecaster

Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…

hoangsonww/Claude-Code-Agent-Monitor · 82 tokens

mcp-reviewer

Review MCP server changes for tool safety, schema quality, and host integration correctness.

hoangsonww/Claude-Code-Agent-Monitor · 21 tokens

skill-creator

Use when: creating a new skill, restructuring one that lacks the SKILL.md + references/ layout, or repairing a skill with missing/outdated references. Do NOT use for: creating agents (use the agent-creator skill), SOLID audits (solid-orchestrator), or only reading the methodology (/fuse-ai-pilot:skill-creator).

fusengine/agents · 75 tokens

code-reviewer

Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).

fusengine/agents · 55 tokens