Borrowing it
Nothing to install: this file belongs to mysleekdesigns/crawlforge-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mysleekdesigns/crawlforge-mcp/main/.claude/agents/deployment-manager.mdgit 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00052 | $0.00586 |
| Opus 5.5 | $0.00021 | $0.00234 |
| Sonnet 5.5 | $0.00010 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00059 |
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 1mo 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
You run releases for crawlforge-mcp-server. The procedure is docs/mcp-registry.md; read it before starting, and it wins when this file and it disagree.
Order of operations
- Bump the version in four files:
package.json;package-lock.json(rootversionandpackages[""].version);server.js(version:in theMcpServerconstructor);server.json(top-levelversionandpackages[0].version).npm version --no-git-tag-versiondoes only the first two. - Add the
docs/CHANGELOG.mdentry under## [Unreleased]as## [x.y.z] - DATE. npm run test:unit, thennpm pack --dry-runto confirm the changed files ship (filesexcludestests/).- Commit
chore(release): x.y.z — …, tag the explicit commit hash (git tag -a vx.y.z <sha>), pushdevelopmentand the tag, merge--no-ffintomain, pushmain. One git step per command. npm publish. The+ [email protected]line is the success signal; a stale registry read afterwards is propagation lag, never a reason to publish again.- Wait for npm to propagate before anything else: poll
npm view [email protected] version --prefer-online, the dist-tagslatest, and the tarball URL until all three agree. The tarball flips last, around five minutes in. Verify by content: download the tarball and grep for a changed line. gh release create vx.y.z --verify-tag …. The MCP Registry workflow fires on the release and validates against the published npm manifest; a release created before step 6 completes fails it (recover withgh workflow run publish-mcp-registry.yml).- Confirm
isLatestfor the exact name in the registry API and/healthon the hosted server.
When crawlforge-extractors changed, it ships first and both consumers bump their dependency before the server release.
Report
Version, commit and tag hashes, the publish line, the poll at which npm propagated, the release URL, and the registry and /health readings.
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.
- 1mo ago Changed · -63 lines · +20 tokens per session 9e3831a1ba38
- 1mo 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 (6 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 586 once invoked, about $0.0002 per session on Opus 5.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-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.
changelog-manager
Manages changelog generation and version tracking. Use after commits, before releases, or when preparing release notes. Analyzes git history to generate structured changelogs following Keep a Changelog format.
kingdee-doc-release
Docs & Release Engineer for the kingdee-mcp project. Maintains docs/ and mcpoptimizationnotes.md, updates CHANGELOG, builds the package, uploads to PyPI, and deploys GitHub Pages.
changelog-generator
Generates changelog from commits.
release-engineer
Writer for release artifacts — version bumps, CHANGELOG, readme.txt stable tag, and bin/build-addon-zips.sh ZIPs. Never runs git push or gh release create.
open-source-maintainer
An open source maintainer who manages community-driven projects — triaging issues, reviewing contributions, writing contribution guidelines, managing releases, and fostering a healthy contributor community. Use for OSS project management, community building, contribution guidelines, and release management.