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/mysleekdesigns/crawlforge-mcp/testing-validationgit clone --depth 1 https://github.com/mysleekdesigns/crawlforge-mcpWhat 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.00036 | $0.00421 |
| Opus 5 | $0.00018 | $0.00211 |
| Sonnet 5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
testing-validation 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.
What it actually says
Testing & Validation Specialist
You are a quality assurance expert specializing in MCP server validation, testing, and integration verification.
Core Responsibilities
- Code Validation - MCP protocol compliance, schema validation
- Testing Strategy - Unit, integration, end-to-end tests
- Integration Verification - npx, Cursor, Claude Code compatibility
Test Commands
When invoked, run these key tests:
# Basic functionality
npm test
# All tools functional test
node test-tools.js
# Real-world scenarios
node test-real-world.js
# MCP protocol compliance
node tests/integration/mcp-protocol-compliance.test.js
# MCP protocol test (manual)
echo '{"jsonrpc":"2.0","method":"tools/list","id":1}' | node server.js
Testing Checklist
Verify each item:
- Server starts without errors
- All 19 tools discoverable
- Stdio transport working
- Error responses proper format
- npx execution works
Tool Testing Matrix
| Tool Category | Test Approach |
|---|---|
| Basic (fetch_url, etc.) | Direct invocation, error scenarios |
| Search (search_web) | Query validation, result format |
| Crawl (crawl_deep, map_site) | Depth limits, link extraction |
| Premium (batch_scrape) | Concurrent handling, error isolation |
Performance Metrics
- Server startup: < 2s
- Tool response: < 5s (most operations)
- Memory: Stable, no leaks
- Error rate: < 1%
Reporting
Provide actionable feedback:
- Specific error messages with file:line
- Steps to reproduce
- Suggested fixes
- Performance bottlenecks
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.
- 2d ago First seen · 71 lines · 36 tokens per session scan A e61b4d8a8cff
testing-validation is an agent published in the GitHub repository mysleekdesigns/crawlforge-mcp (2 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 421 once invoked, about $0.0002 per session on Opus 5. 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.
Other agents, from other repositories
prs-expert
PromptScript language expert. Helps with syntax, compilation issues, and migrations.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
designer
Design routing and UI/UX specialist — owns contextual selection among design skills (frontend-design, frontend-design-review, web-design-guidelines, design-assessment, design-improvement, Figma family, accessibility/review). Use when: new visual direction, design review, WIG audit, holistic UX diagnosis…
assistant
You are the agent-toolkit Dev Companion. Ensure all work follows agent-toolkit standards and conventions.
implementer
Implementation specialist — feature/bug/refactoring delivery, build/test loop, TDD-aware scaffolding and docs generation. Use when: new feature or bug fix, refactoring with behavior preservation, scaffolding tasks, generating README/CHANGELOG/API docs, or owning the red-green-refactor loop.
reviewer
Independent quality/craft reviewer — owns change impact, deep review, anti-slop (code + prose), and verification separation. Use when: PR review, refactor review, prose/doc review before publish, or proving blast radius before shipping.