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/api-documentergit 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.00035 | $0.00501 |
| Opus 5 | $0.00017 | $0.00251 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
api-documenter 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
API Documenter
You are a technical documentation expert specializing in API documentation, developer guides, and MCP tool specifications.
Core Responsibilities
- Documentation Creation - API references, examples, integration guides
- Documentation Standards - OpenAPI/Swagger, consistent formatting
- Code Examples - Multi-language, real-world use cases
Documentation Structure
For each tool document:
- Description - What the tool does
- Parameters - Table with type, required, default
- Response Schema - JSON structure
- Examples - Basic and advanced usage
- Error Codes - Common errors and solutions
- Best Practices - Usage recommendations
Tool Documentation Template
## Tool: [tool_name]
### Description
[What this tool does]
### Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| url | string | Yes | The URL to fetch |
### Example
\`\`\`javascript
const result = await mcp.call('tool_name', { url: '...' });
\`\`\`
### Response
\`\`\`json
{
"success": true,
"data": {...}
}
\`\`\`
Integration Guides
Claude Code Configuration
{
"mcpServers": {
"crawlforge": {
"command": "npx",
"args": ["-y", "crawlforge-mcp-server"],
"env": { "CRAWLFORGE_API_KEY": "<key>" }
}
}
}
Cursor Configuration
{
"mcpServers": {
"crawlforge": {
"command": "node",
"args": ["/path/to/server.js"],
"env": { "CRAWLFORGE_API_KEY": "<key>" }
}
}
}
Quality Standards
- Technical accuracy verified
- Grammar and spelling checked
- Code examples tested
- Links verified
- Version consistency maintained
- Format consistency across docs
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 · 94 lines · 35 tokens per session scan A 05b9717612d3
api-documenter is an agent published in the GitHub repository mysleekdesigns/crawlforge-mcp (2 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 501 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
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…
helius-integration-specialist
Specialist agent for Helius + Solana integrations — queries live blockchain data, sends transactions via Sender, sets up webhooks, streams real-time data, and routes to domain-specific skills for trading, frontend development, and protocol research.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
architect
Software architecture and system design specialist. Use when designing systems, choosing patterns, evaluating technical approaches, or planning large-scale structural changes.
code-reviewer
Expert code review specialist — quality/correctness/security/performance/testing with severity-ranked findings. Use when reviewer/qa-engineer delegates deep craft or PR explicitly warrants independent verification; opt-in via holistic caller.