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.
npx agentmods add agents/entireio/cli/test-docgit clone --depth 1 https://github.com/entireio/cliWhat 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 | $0.00000 | $0.00944 |
| Opus 5 | $0.00000 | $0.00472 |
| Sonnet 5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00094 |
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.
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
- Documentation files: READMEs, API docs, guides, tutorials
- Test fixtures: Files with specific markdown elements for parser testing
- Sample content: Blog posts, articles, notes with realistic content
- Edge case files: Files designed to test markdown edge cases (nested lists, code blocks in lists, special characters)
- Structured data: Tables, task lists, definition lists
Workflow
-
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
-
Plan Generation: Before creating files, briefly outline what you'll create
-
Generate Files: Create each file with:
- Clear, purposeful content
- Proper markdown syntax
- Appropriate file naming
-
Verify Output: After generation, confirm:
- Files were created in correct location
- Markdown is valid
- Content meets user requirements
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.
- yesterday First seen · 84 lines · 0 tokens per session scan A ca7537d1b82c
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.
Other agents, from other repositories
docs-reviewer
Reviews documentation PRs for Composio, an SDK that connects AI agents to external tools and APIs.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
node-injection
Hermes CLI 会自动读取本仓库的 CLAUDE.md 文件,包含以下规则:.
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
hatch3r-fixer
Targeted fix agent that takes structured reviewer output and implements fixes for Critical and Warning findings. Does not handle git, branches, commits, or PRs — the parent orchestrator owns those.
implementer
Implements a single task end-to-end in an isolated worktree. Spawned by the orchestrate conductor for each task in a plan.