document-mcp: Command for Claude Code

.claude/commands/1-research.md

1-research is a command for Claude Code from clchinkc/document-mcp. It costs 0 tokens per session (93 once invoked), scanned A, original, MIT.

A command that reviews a project's source code and tests to understand its design, patterns, trade-offs, and coverage. It uses multiple agents working in parallel.

In plain words
What is it for?
Use it for implementation reviews, test-strategy reviews, and planning improvements to reliability or maintainability.
Why use it?
It helps reveal architectural choices, code-quality issues, and testing gaps before implementation changes are made.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is clchinkc/document-mcp's own configuration. It tells Claude Code how to work on document-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything document-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to clchinkc/document-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/clchinkc/document-mcp/main/.claude/commands/1-research.md
Clone the repo
git clone --depth 1 https://github.com/clchinkc/document-mcp

Made for: Claude Code.

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 1-research

README.md
[![agentmods](https://agentmods.dev/badge/commands/clchinkc/document-mcp/1-research/github.svg)](https://agentmods.dev/commands/clchinkc/document-mcp/1-research)
Your own site
<a href="https://agentmods.dev/commands/clchinkc/document-mcp/1-research"><img src="https://agentmods.dev/badge/commands/clchinkc/document-mcp/1-research/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 1-research

Your own site · 80×15
<a href="https://agentmods.dev/commands/clchinkc/document-mcp/1-research"><img src="https://agentmods.dev/badge/commands/clchinkc/document-mcp/1-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 93 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.00000 $0.00093
Opus 5.5 $0.00000 $0.00037
Sonnet 5.5 $0.00000 $0.00019
Haiku 4.5 $0.00000 $0.00009

Measured 2mo ago against content hash 317f9ded6d18, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

1-research 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 2mo 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.

.claude/commands/1-research.md · 5 lines

What it actually says

Research (Multi-Agent Parallel)

Implementation Analysis: Examine all implementation files (src/) for fundamental principles, concrete patterns, and system design. Focus on complexity vs. usefulness vs. extensibility trade-offs, architectural decisions, and code quality patterns.

Testing Analysis: Review all test files (tests/) for testing purpose, pass/fail conditions, coverage gaps, and effectiveness. Optimize testing strategy to ensure implementation correctness with minimal resource usage and maximum reliability.

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. 2mo ago First seen · 5 lines · 0 tokens per session scan A 317f9ded6d18

Subscribe to this mod's changes

1-research is a command published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 93 tokens. 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 commands, from other repositories

councilreview

You are a panel of 8 independent expert reviewers. Each expert analyzes the same diff but from their specialized perspective. Experts do not coordinate -- they review independently and may contradict each other. After all reviews, an Auto-Fix phase applies safe fixes for LOW/MEDIUM findings.

whiteknightonhorse/APIbase · 0 tokens

codexreview

You are a hostile code reviewer. Your job is to find bugs, vulnerabilities, and defects. Not to compliment code.

whiteknightonhorse/APIbase · 0 tokens

ultra-agents

Autonomous multi-round review + fix loop — no per-round approval.

ZoeLinUTS/MagicTeX-mcp · 0 tokens

reply_to_comment

Call the replytocomment MCP tool to add a threaded reply to an existing comment. Read the comment id and the reply text from $ARGUMENTS. Use this to respond to my feedback, or as the author/defender role in a review thread before I resolve it. If no id is given, ask me which comment to reply to.

ZoeLinUTS/MagicTeX-mcp · 0 tokens

resolve_comment

Call the resolvecomment MCP tool to mark a comment as resolved once the edit is made. Read the comment id and a one-line note from $ARGUMENTS. If no id is given, first call checkcomments, make the edit each one asks for, then resolve each with a short note. Resolved comments turn green in the workspace so I can review…

ZoeLinUTS/MagicTeX-mcp · 0 tokens

show_diff

Call the showdiff MCP tool to show me a side-by-side visual diff (it returns an image in the chat). If I passed a checkpoint sha in $ARGUMENTS, diff that checkpoint; otherwise show my current uncommitted changes.

ZoeLinUTS/MagicTeX-mcp · 17 tokens