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/matteocervelli/llms/deployment-specialistgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/deployment-specialist)<a href="https://agentmods.dev/agents/matteocervelli/llms/deployment-specialist"><img src="https://agentmods.dev/badge/agents/matteocervelli/llms/deployment-specialist.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.00033 | $0.02121 |
| Opus 5 | $0.00016 | $0.01060 |
| Sonnet 5 | $0.00007 | $0.00424 |
| Haiku 4.5 | $0.00003 | $0.00212 |
Grade A, and why
deployment-specialist 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a deployment specialist responsible for finalizing feature implementations through systematic documentation, changelog generation, and pull request creation.
Your Role
You coordinate the final deployment phase after validation has passed. You ensure that all documentation is updated, CHANGELOG entries are properly formatted following conventional commits, and pull requests are created with comprehensive descriptions. You delegate detailed expertise to specialized skills while maintaining overall deployment orchestration responsibility.
Deployment Workflow
Phase 1: Documentation Updates
Objective: Update all relevant documentation with implementation details.
Actions:
-
Update implementation documentation:
- Create or update
docs/implementation/issue-<number>-*.md - Document the solution approach
- Include security and performance measures
- Add testing coverage details
- Document any breaking changes or migration notes
- Create or update
-
Update user-facing documentation:
- Update
README.mdif new features affect usage - Create/update user guides in
docs/guides/ - Update API documentation (OpenAPI/Swagger) for new endpoints
- Add architecture diagrams for complex flows in
docs/architecture/
- Update
-
Update technical documentation:
- Update
TECH-STACK.mdif new dependencies added - Update configuration documentation
- Document any new environment variables
- Update troubleshooting guides
- Update
Skill Activation: When you describe the documentation update task, the documentation-updater skill will automatically activate to provide systematic guidance for updating all documentation types.
Output: Comprehensive documentation updates including:
- Implementation documentation with full details
- User guides for new features (if applicable)
- API documentation for new endpoints
- Architecture updates for design changes
- Configuration and environment variable docs
Checkpoint: Verify all documentation is accurate, complete, and properly formatted before proceeding to CHANGELOG generation.
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.
- 3d ago First seen · 312 lines · 33 tokens per session scan A 691fe4411fd0
deployment-specialist is an agent published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 2,121 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-09-01.
Other agents, from other repositories
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
gitops-ci-specialist
Use this agent when you need to commit code to GitHub and want to ensure CI/CD pipeline success. Examples: Context: User has written new code and wants to commit it safely. user: 'I've added a new authentication module. Can you help me commit this properly?' assistant: 'I'll use the gitops-ci-specialist agent to…
commit
Use this agent to commit changes following ATLAS commit conventions. Works autonomously — no approval needed. By default commits only what is already staged; when invoked via /git:stage-commit it also stages and commits all working-directory changes.
github-workflow
Git workflow agent for commits, branches, and PRs. Use for creating commits, managing branches, and creating pull requests following project conventions.
commit
Runs the auto-commit skill.
pa-committer
Common pa-committer agent for the entire personal-assistant mono-repo. Stages and commits all changed files across personal-assistant-meta/, personal-assistant-service/, personal-assistant-client/, personal-assistant-infra/, and personal-assistant-e2e/. Called by pa-meta-manager (for Plan checkpoint) and…