agentmods.dev

docs-reviewer

A review agent for documentation pull requests in agentdeck. It checks examples, commands, settings, links, writing style, and whether the documentation matches the actual product.

In plain words
What is it for?
Approving or requesting changes on an agentdeck docs-site pull request, including checking Python examples and running the project's verification command.
Why use it?
It catches inaccurate instructions, broken examples, unnecessary verbosity, and navigation problems before documentation is merged.

Agent for Claude Code

2 2d ago A scan 33 tokens original MIT
View the source file agentdecksdk/agentdeck
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 agents/agentdecksdk/agentdeck/docs-reviewer
Clone the repo
git clone --depth 1 https://github.com/agentdecksdk/agentdeck

Made for: Claude Code.

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 311 The whole file, excluding the scripts and references it only reads on demand.
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.00033 $0.00311
Opus 5 $0.00016 $0.00156
Sonnet 5 $0.00007 $0.00062
Haiku 4.5 $0.00003 $0.00031

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

Security

Grade A, and why

docs-reviewer 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.

.claude/agents/docs-reviewer.md · 27 lines

What it actually says

You review one docs-site PR as the gate before merge.

Review Checks

  1. Truthfulness against Code:
    • Check every code snippet, endpoint, setting (AGENTDECK_*), and CLI command against the actual implementation.
    • Ensure all Python code fences are tested and valid.
  2. Product Philosophy & IA:
    • Adheres to docs/spec.md Part II (Answer first, code before theory, progressive disclosure).
    • Verifies the page teaches user intent and public APIs (Deck, Run, Agent), NOT internal plumbing.
  3. Anti-Verbosity:
    • Flag fluff, filler words ("simply", "just", "easy"), and repetitive explanations.
    • Ensure text is dense with signal and gets straight to the point.
  4. Links & Navigation:
    • Check all internal links and navigation entries.
  5. Gate & Output Style:
    • Run make check to verify anti-rot tests.
    • Keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.

Return: approve or request changes with a concise, ranked list of confirmed findings (file:line, issue, concrete fix).

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 · 27 lines · 33 tokens per session scan A 3f20563b9838

Subscribe to this mod's changes

docs-reviewer is an agent published in the GitHub repository agentdecksdk/agentdeck (2 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 311 once invoked, about $0.0002 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.

Code reviewPlanningWriting and docsagent-frameworkagent-observabilityagent-runtimeagent-workflowsagentic-aiai-agents
Related

Other agents, from other repositories

building-agents

Create intelligent agents that connect to MCP servers, discover tools automatically, and execute tasks with full observability.

promptise-com/Foundry · 0 tokens

reasoning-patterns

Every Promptise agent is powered by a Reasoning Graph. By default, buildagent() creates a ReAct graph (single node with tools) — and that default is smart by default: it manages context automatically (contextscope="auto"), so simple tasks are unchanged and deep tool loops stay token-efficient without you choosing…

promptise-com/Foundry · 0 tokens

cross-agent

Enable agents to delegate tasks to peer agents using auto-generated tools like askagentresearcher and broadcasttoagents.

promptise-com/Foundry · 0 tokens

server-specs

Configure how agents connect to MCP servers using StdioServerSpec for local servers and HTTPServerSpec for remote ones.

promptise-com/Foundry · 0 tokens

superagent-files

Define agents declaratively using .superagent YAML files -- configure model, servers, memory, sandbox, and cross-agent references in a single file.

promptise-com/Foundry · 0 tokens

network-server

NetworkServer has been removed from Promptise. For production deployment of agents, see the Agent Runtime documentation.

promptise-com/Foundry · 0 tokens