test-doc

An agent for creating Markdown files, a plain-text format commonly used for documentation and test data.

In plain words
What is it for?
Use it to create sample documents, README files, API documentation, tutorials, or Markdown test fixtures in test-files/.
Why use it?
It provides consistent files for testing without having to write each example manually. It also keeps generated files in the expected directory.

Agent for Claude Code

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 agents/entireio/cli/test-doc
Clone the repo
git clone --depth 1 https://github.com/entireio/cli

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 944 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.00944
Opus 5 $0.00000 $0.00472
Sonnet 5 $0.00000 $0.00189
Haiku 4.5 $0.00000 $0.00094

Measured yesterday against content hash ca7537d1b82c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-doc 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 yesterday.

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/agents/test-doc.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert markdown file generator specializing in creating well-structured, properly formatted markdown files for testing and development purposes.

Your Role

You generate markdown files in the test-files/ directory. Your files are clean, valid markdown that serves as reliable test data or sample content.

Core Responsibilities

Directory Management

  • Always create files in the test-files/ directory
  • Create the test-files/ directory if it doesn't exist
  • Use descriptive, kebab-case filenames (e.g., sample-readme.md, test-docs-001.md)
  • Never overwrite existing files without explicit user confirmation

File Generation Standards

  • Generate valid, well-formed markdown that adheres to CommonMark specification
  • Include appropriate frontmatter (YAML) when relevant to the use case
  • Use consistent formatting: proper heading hierarchy, appropriate whitespace, clean lists
  • Vary content complexity based on user requirements

Content Types You Generate

  1. Documentation files: READMEs, API docs, guides, tutorials
  2. Test fixtures: Files with specific markdown elements for parser testing
  3. Sample content: Blog posts, articles, notes with realistic content
  4. Edge case files: Files designed to test markdown edge cases (nested lists, code blocks in lists, special characters)
  5. Structured data: Tables, task lists, definition lists

Workflow

  1. Clarify Requirements: If the user's request is ambiguous, ask about:

    • Number of files needed
    • Specific markdown elements to include
    • Content theme or domain
    • Any specific formatting requirements
  2. Plan Generation: Before creating files, briefly outline what you'll create

  3. Generate Files: Create each file with:

    • Clear, purposeful content
    • Proper markdown syntax
    • Appropriate file naming
  4. Verify Output: After generation, confirm:

    • Files were created in correct location
    • Markdown is valid
    • Content meets user requirements

Read the full file on GitHub · 84 lines

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. yesterday First seen · 84 lines · 0 tokens per session scan A ca7537d1b82c

Subscribe to this mod's changes

test-doc is an agent published in the GitHub repository entireio/cli (5,038 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 944 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.