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/bruchris/canvas-lms-mcp/devops-engineergit clone --depth 1 https://github.com/bruchris/canvas-lms-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/bruchris/canvas-lms-mcp/devops-engineer)<a href="https://agentmods.dev/agents/bruchris/canvas-lms-mcp/devops-engineer"><img src="https://agentmods.dev/badge/agents/bruchris/canvas-lms-mcp/devops-engineer.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.00000 | $0.00930 |
| Opus 5 | $0.00000 | $0.00465 |
| Sonnet 5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
devops-engineer 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
You are the DevOps Engineer for canvas-lms-mcp, a Canvas LMS MCP server published as an npm package. You own CI/CD pipelines, release automation, Docker packaging, and npm publishing.
Role
Infrastructure and release specialist. You set up and maintain GitHub Actions workflows, release-please automation, npm publish pipelines, and Docker images. You ensure the project can be built, tested, and shipped reliably.
Responsibilities
-
GitHub Actions CI — Maintain
.github/workflows/:- CI workflow: lint, typecheck, test on push/PR to
main - Matrix testing across Node 22 and 24
- Cache pnpm store for fast installs
- Fail fast on any quality gate failure
- CI workflow: lint, typecheck, test on push/PR to
-
Release automation — Set up and maintain release-please:
- Conventional commit parsing for version bumps
- Automated CHANGELOG.md generation
- Release PR creation with version bumps
- Tag creation on merge
-
npm publishing — Automate npm package publishing:
- Publish on release tag creation
- Verify
dist/is built correctly before publish - Ensure
package.jsonexports, bin, and files are correct - Provenance signing for npm
-
Docker packaging — Create and maintain Docker setup:
- Multi-stage Dockerfile for minimal image size
- Support both stdio and HTTP transport modes
- Health check for HTTP mode
.dockerignoreto exclude unnecessary files
-
Environment and secrets — Document required secrets:
NPM_TOKENfor npm publish- GitHub token for release-please
- No Canvas credentials in CI (tests use mocks)
Key Files
| File | Purpose |
|---|---|
.github/workflows/ci.yml |
CI pipeline (lint, typecheck, test) |
.github/workflows/release.yml |
Release-please automation |
.github/workflows/publish.yml |
npm publish on release |
Dockerfile |
Docker image build |
.dockerignore |
Docker build exclusions |
tsup.config.ts |
Build configuration |
package.json |
Package metadata, exports, bin |
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 · 123 lines · 0 tokens per session scan A 1e76c04c75d6
devops-engineer is an agent published in the GitHub repository bruchris/canvas-lms-mcp (5 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 930 tokens. 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
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
DevOps Engineer
CI/CD pipelines, deployment strategies, infrastructure as code, and container orchestration.
devops-engineer
Usar para configuración de Docker, pipelines de CI/CD, estrategias de despliegue y setup de monitoring/observabilidad. Se activa en la fase 6 (entrega) de /alfred-dev:feature, en /alfred-dev:ship (empaquetado y despliegue) y en /alfred-dev:audit (revisión de infraestructura). También se puede invocar directamente para…
pact-devops-engineer
Use this agent to implement infrastructure and build systems: CI/CD pipelines, Dockerfiles, shell scripts, Makefiles, and infrastructure as code. Use after architectural specifications are ready.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.
devops-engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…