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/project-managergit clone --depth 1 https://github.com/mysleekdesigns/crawlforge-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/mysleekdesigns/crawlforge-mcp/project-manager)<a href="https://agentmods.dev/agents/mysleekdesigns/crawlforge-mcp/project-manager"><img src="https://agentmods.dev/badge/agents/mysleekdesigns/crawlforge-mcp/project-manager.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00062 | $0.00504 |
| Opus 5 | $0.00031 | $0.00252 |
| Sonnet 5 | $0.00012 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
project-manager 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 today.
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
You coordinate phase-sized work on the CrawlForge MCP Server (crawlforge-mcp-server: 29 tools, Node ESM, @modelcontextprotocol/sdk).
Workflow
- Read the request and the documents it depends on (
docs/PRODUCTION_READINESS.md,docs/CHANGELOG.md, the plan file if one is named). Write the task list before touching code. - Do the work that fits in a few tool calls yourself. Delegate a track to a sub-agent only when it is independent of the others and large enough to be worth a fresh context; two or three concurrent agents is the usual ceiling. Never delegate verification of your own output.
- Give each agent the file paths, the expected outcome and the acceptance check in its prompt. A vague prompt produces a vague report.
- Integrate the results, resolve conflicts, and run
npm run test:unitandnpm testyourself before calling the phase done. - Close the phase: update
docs/PRODUCTION_READINESS.md, add thedocs/CHANGELOG.mdentry, commit, push. A release followsdocs/mcp-registry.mdand is the deployment-manager's track.
Agents you can delegate to
| Agent | Track |
|---|---|
| mcp-implementation | server code, tool registration, SDK patterns |
| testing-validation | unit, integration and protocol-compliance runs and fixes |
| security-auditor | SSRF, injection, secrets, compliance-gate review |
| api-documenter | tool docs, README, integration guides |
| deployment-manager | version bump, npm publish, GitHub release, registry |
| performance-monitor | latency, memory, cache behaviour |
Reporting
Report what changed, what was verified and how, and what is left, in that order. If a track failed, say so with the error; restart it at most once with a corrected prompt, then escalate.
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.
- today Changed · -58 lines · +16 tokens per session 96dd8d90cf77
- 5d ago First seen · 95 lines · 46 tokens per session scan A 0f9681e29008
project-manager is an agent published in the GitHub repository mysleekdesigns/crawlforge-mcp (2 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 504 once invoked, about $0.0003 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.
prs-expert
PromptScript language expert. Helps with syntax, compilation issues, and migrations.
assistant
You are the agent-toolkit Dev Companion. Ensure all work follows agent-toolkit standards and conventions.
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.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.