Borrowing it
Nothing to install: this file belongs to rossumai/rossum-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rossumai/rossum-agents/master/.claude/commands/ds-review-readme.mdgit clone --depth 1 https://github.com/rossumai/rossum-agentsWrote 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/rossumai/rossum-agents/ds-review-readme)<a href="https://agentmods.dev/commands/rossumai/rossum-agents/ds-review-readme"><img src="https://agentmods.dev/badge/commands/rossumai/rossum-agents/ds-review-readme/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/rossumai/rossum-agents/ds-review-readme"><img src="https://agentmods.dev/badge/commands/rossumai/rossum-agents/ds-review-readme.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.00000 | $0.00689 |
| Opus 5 | $0.00000 | $0.00345 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
ds-review-readme 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review & Improve README
Goal: Audit all README files from open-source maintainer perspective, ensure style consistency across them, then implement approved improvements.
Review Dimensions
| Dimension | Focus Areas |
|---|---|
| First Impression | Hook in first 3 lines, clear value proposition, visual appeal |
| Structure | Logical flow, scannable sections, appropriate depth |
| Onboarding | Installation steps, quick start, copy-paste examples |
| Trust Signals | Badges, license, contribution info, maintenance activity |
| Discoverability | Keywords, project positioning, comparison to alternatives |
Review Checklist
| Category | Check For |
|---|---|
| Opening | One-line description, what problem it solves, who it's for |
| Visuals | Logo/banner, badges (build, coverage, version), screenshots/GIFs if applicable |
| Installation | All methods (pip, npm, etc.), prerequisites clearly stated |
| Quick Start | Working example within 30 seconds of reading |
| Usage | Common use cases with code examples, expected output shown |
| API Reference | Link to docs or inline reference for key functions |
| Configuration | Environment variables, config files, options tables |
| Contributing | Link to CONTRIBUTING.md or inline guidelines |
| License | Clearly stated, link to LICENSE file |
| Support | Where to get help, issue templates, discussions |
| Badges | Appropriate badges (CI status, version, downloads, license) |
| Links | No broken links, relative paths for repo files |
Best Practices
| Practice | Implementation |
|---|---|
| Inverted pyramid | Most important info first, details later |
| Scannable | Headers, bullet points, tables over prose |
| Code blocks | Syntax highlighting, copy-paste ready |
| Minimal jargon | Accessible to newcomers, define terms |
| Show don't tell | Examples over explanations |
| Keep current | No outdated version numbers or deprecated features |
Approach
| Step | Action |
|---|---|
| Discover | Find all README files in the project (root, subdirectories, packages) |
| Audit | Read each README, identify gaps across all dimensions |
| Consistency | Compare style, formatting, structure across all READMEs; flag inconsistencies |
| Compare | Check against top open-source READMEs in same domain |
| Prioritize | Rank findings by impact (Critical → High → Medium → Low) |
| Present | Show findings with specific recommendations |
| Confirm | Use AskUserQuestion to approve implementation scope |
| Implement | Apply approved changes |
| Verify | Ensure links work and examples are accurate |
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.
- 11d ago First seen · 87 lines · 0 tokens per session scan A 02043bf17ecc
ds-review-readme is a command published in the GitHub repository rossumai/rossum-agents (11 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 689 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-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.