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.
git clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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.
[](https://agentmods.dev/commands/davistroy/claude-marketplace/assess-document)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/assess-document"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/assess-document/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.
<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/assess-document"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/assess-document.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00007 | $0.03832 |
| Opus 5 | $0.00003 | $0.01916 |
| Sonnet 5 | $0.00001 | $0.00766 |
| Haiku 4.5 | $0.00001 | $0.00383 |
Grade A, and why
assess-document 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Assessment Command
Perform a comprehensive evaluation of the specified document, identifying gaps, issues, missing content, and areas for improvement. Produce a detailed assessment report.
Input Validation
Required Arguments:
<document-path>- Path to the document to assess
Optional Arguments:
--format [md|json]- Output format (default: md)md: Markdown report with tables and sections (default)json: Structured data with scores, issues array, and recommendations
--focus <dimensions>- Comma-separated list of dimensions to evaluate (default: all dimensions)- Valid dimensions:
completeness,clarity,consistency,specificity,structure,feasibility - Example:
--focus completeness,clarity,specificity - When used, only the specified dimensions are scored and reported
- Overall score is the average of the focused dimensions only
- Valid dimensions:
--no-prompt- Disable interactive prompting for missing arguments (for scripts and CI/CD)
Validation: If the document path is missing:
- If
--no-promptis specified, display the error and exit:
Error: Missing required argument
Usage: /assess-document <document-path> [--format md|json] [--focus <dimensions>] [--no-prompt]
Example: /assess-document PRD.md
Example: /assess-document PRD.md --format json
Example: /assess-document PRD.md --focus completeness,clarity
- Otherwise (default), prompt interactively:
/assess-document requires a document path.
Please provide the path to the document to assess:
> _
(or use --no-prompt to disable interactive prompting)
Wait for the user to provide the document path, then proceed with assessment.
Focus Flag Validation:
If --focus is provided, validate each dimension name. If any are invalid, display:
Error: Invalid focus dimension(s): [invalid-names]
Valid dimensions: completeness, clarity, consistency, specificity, structure, feasibility
Example: /assess-document PRD.md --focus completeness,clarity,specificity
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.
- 10d ago First seen · 473 lines · 7 tokens per session scan A 47f748b52bf0
assess-document is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 3,832 once invoked, about $0.0000 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.
Other commands, from other repositories
brand-generate
Generate an on-brand document from a saved Brand Profile.
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
render-figures
Compile all .tex and .typ figure files in a directory.
harness-onboarding
Generate a human-readable onboarding document from HARNESS.md, AGENTS.md, and REFLECTIONLOG.md — a friendly guide for new team members.