A command that reviews a software product and writes a first-person, step-by-step tutorial about testing it. The tutorial compares the experience of a casual user, an advanced user, and a developer using VibeSolver.

Use it to inspect the latest generated code, test released features, and save a Markdown article in the articles/ folder. The article can include tables, lists, project trees, diagrams, and citations.

It turns a code review into a practical guide that shows readers how to evaluate released features. It also gives the guide a consistent Markdown structure for use in a book about writing software with generated code.

How manavsehgal/vibesolver configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to manavsehgal/vibesolver. 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/manavsehgal/vibesolver/main/.claude/commands/article.md

Clone the repo

git clone --depth 1 https://github.com/manavsehgal/vibesolver

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/manavsehgal/vibesolver/article/github.svg)](https://agentmods.dev/commands/manavsehgal/vibesolver/article)

Your own site

<a href="https://agentmods.dev/commands/manavsehgal/vibesolver/article"><img src="https://agentmods.dev/badge/commands/manavsehgal/vibesolver/article/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/manavsehgal/vibesolver/article"><img src="https://agentmods.dev/badge/commands/manavsehgal/vibesolver/article.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 129 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00129
Opus 5.5	$0.00000	$0.00052
Sonnet 5.5	$0.00000	$0.00026
Haiku 4.5	$0.00000	$0.00013

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

Security

Grade A, and why

article 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/article.md · 2 lines

What it actually says

Ultrathink to review the latest sprint based code generated and then write an article in first person style as step-by-step tutorial to evaluate the released features as a casual user, as a power user, and as a developer using VibeSolver. Write the article in markdown starting at level 2 heading with valid markdown tables, lists, ascii project structure and diagrams where applicable in code fence blocks, and narrative to guide the evaluation. The article is part of a chapter in the book on Vibe Coding so references to code generation, vibe coding, etc. are welcome along with appropriate citations. Save the article appropriately named in articles/ folder.

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.

2mo ago First seen · 2 lines · 0 tokens per session scan A ead2c1c96243

Subscribe to this mod's changes

article is a command published in the GitHub repository manavsehgal/vibesolver (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 129 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.

Writing and docs agent ai aws vibe-coding

article next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
articlemanavsehgal/vibesolver	Command	5	1y ago	MIT	A	0	Claude Code
remote-autopilot-install.v1stakpak/agent	Command	1.9k	4mo ago	Apache-2.0	B	36	Claude Code
statuswtzywkloo/wtcraft	Command	2	1mo ago	Apache-2.0	A	0	Claude Code
docsdocfork/docfork	Command	483	4mo ago	MIT	A	10	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code

vibesolver: Command for Claude Code