agentmods.dev

test-guide

A testing guide and helper for checking VMark, a text editor, across its major features.

In plain words
What is it for?
Use it to test formatting, file operations, autosave, history, search, modes, settings, images, diagrams, and other VMark features.
Why use it?
It organizes manual checks so important editor behavior is tested systematically rather than informally.

Command for Claude Code

544 2d ago A scan 0 tokens original ISC
View the source file xiaolai/vmark
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 commands/xiaolai/vmark/test-guide
Clone the repo
git clone --depth 1 https://github.com/xiaolai/vmark

Made for: Claude Code.

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 451 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.00000 $0.00451
Opus 5 $0.00000 $0.00226
Sonnet 5 $0.00000 $0.00090
Haiku 4.5 $0.00000 $0.00045

Measured 2d ago against content hash 8bcc402de9c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-guide 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 2d 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/test-guide.md · 43 lines

What it actually says

Manual Testing Guide

Open the comprehensive testing guide and help the user test VMark features.

Instructions

  1. Read the testing guide at dev-docs/testing/comprehensive-testing-guide.md (create the directory if it does not yet exist)
  2. Present a summary of test categories to the user
  3. If the user specifies a category, show those specific tests
  4. Help track test results if requested

Test Categories

  1. Text Formatting - Bold, italic, code, strikethrough, nested marks
  2. Atomic Nodes - Footnote and math selection behavior
  3. Mode Switching - Cursor sync between WYSIWYG and Source (F7)
  4. File Operations - New, open, save, save as, close
  5. Auto-Save - Automatic saving with configurable interval
  6. Document History - Version history, revert, pruning
  7. UI Components - Status bar, sidebar, title bar
  8. Slash Menu - "/" trigger menu for block insertion
  9. Search - Find and replace (Cmd+F)
  10. Focus/Typewriter - Focus mode (F8), Typewriter mode (F9)
  11. Settings - Themes, fonts, CJK options
  12. Unicode - CJK text, emoji, special characters
  13. Popups - Link, image, footnote popups
  14. Images - Paste, drag-drop, context menu
  15. Code/Diagrams - Code blocks, LaTeX, Mermaid

Quick Start

Ask the user which category they want to test, then:

  1. Show the relevant test cases from the guide
  2. Help them execute tests if app is running (use Tauri MCP)
  3. Record results

Files

  • Main guide: dev-docs/testing/comprehensive-testing-guide.md
  • Cursor sync details: dev-docs/testing/cursor-sync-manual-testing.md
  • Atomic node details: dev-docs/testing/atomic-node-selection-testing.md
  • Auto-save details: dev-docs/testing/auto-save-history-testing.md
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. 2d ago First seen · 43 lines · 0 tokens per session scan A 8bcc402de9c6

Subscribe to this mod's changes

test-guide is a command published in the GitHub repository xiaolai/vmark (544 stars, last pushed 2d ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 451 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.

ResearchTesting
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens