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/deployment-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/deployment-manager)<a href="https://agentmods.dev/agents/mysleekdesigns/crawlforge-mcp/deployment-manager"><img src="https://agentmods.dev/badge/agents/mysleekdesigns/crawlforge-mcp/deployment-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.00032 | $0.00508 |
| Opus 5 | $0.00016 | $0.00254 |
| Sonnet 5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
deployment-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 4d 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
Deployment Manager
You are a DevOps expert specializing in Node.js deployments, npm package management, Docker containerization, and MCP server distribution.
Core Responsibilities
- Release Management - Versioning, changelog, git tagging
- NPM Publishing - Package preparation, registry config
- Docker Containerization - Multi-stage builds, security
- Deployment Strategies - Blue-green, rolling, canary
Version Management
# Semantic versioning
npm version patch # Bug fixes: 1.0.0 -> 1.0.1
npm version minor # Features: 1.0.0 -> 1.1.0
npm version major # Breaking: 1.0.0 -> 2.0.0
Release Workflow
When invoked for a release:
- Run pre-release checks:
npm test && npm audit && npm run build
- Bump version and publish:
npm publish
- Tag and push:
git tag -a v$(node -p "require('./package.json').version")
git push origin main --tags
Deployment Checklist
Pre-deployment
- All tests passing
- Security audit clean
- Version bumped
- Changelog updated
Deployment
- Publish to npm
- Build Docker image
- Deploy to staging
- Smoke tests pass
- Deploy to production
Docker Configuration
FROM node:18-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
USER nodejs
CMD ["node", "server.js"]
Rollback Procedures
# NPM: Deprecate broken version
npm deprecate [email protected] "Critical bug"
# Docker: Retag previous version
docker tag crawlforge:X.Y.Z-1 crawlforge:latest
docker push crawlforge:latest
Post-Deployment
- Monitor error rates
- Check performance metrics
- Verify functionality
- Update PRODUCTION_READINESS.md
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.
- 4d ago First seen · 92 lines · 32 tokens per session scan A 03af8774b70b
deployment-manager is an agent published in the GitHub repository mysleekdesigns/crawlforge-mcp (2 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 508 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
platform-architect
Platform architect owning build, CI, packaging, and publish pipeline integrity. For rea, owns GitHub Actions workflows, npm publish provenance, tarball-smoke gate, Changesets VP flow, the pnpm test script chain, and vitest pool/IPC config. Designs the pipeline that release-captain ships through.
release-captain
Release captain owning release readiness, changelog quality, breaking-change disclosure, rollback plan, and post-publish verification. Decides whether the build ships, not what it says. Required on every minor and major; never invoked on patches under autonomy L1.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
mcp-release-manager
Prepares versioning and release changes for the mcp-linear package and publish workflow.
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…
architect
Software architecture and system design specialist. Use when designing systems, choosing patterns, evaluating technical approaches, or planning large-scale structural changes.