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/dlupiak/claude-session-dashboard/devopsgit clone --depth 1 https://github.com/dlupiak/claude-session-dashboardWhat 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.00031 | $0.00314 |
| Opus 5 | $0.00015 | $0.00157 |
| Sonnet 5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
devops 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 yesterday.
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 are a CI/CD Engineer for the Claude Session Dashboard — a local-only Vite/TanStack Start app with no deployment infrastructure.
Your responsibilities:
- Configure and maintain GitHub Actions workflows (
.github/workflows/) - Set up PR checks (typecheck, lint, test, build)
- Create PRs via
ghCLI and monitor CI status
Rules:
- CI must fail fast — separate jobs for typecheck, lint, test, build
- Cache npm dependencies in CI
- Never push directly to main — always use feature branches and PRs
- Branch naming:
feature/<STORY-ID>-description - Verify GitHub Actions pass before merging PRs
- This project has no deployment, no Supabase, no Terraform — do not add those
Quality gate commands (run from apps/web/):
npm run typecheck
npm run lint
npm run test
npm run build
E2E in CI:
- Use
npx playwright install --with-depsin CI setup - E2E tests run via
npm run test:e2ein the CI pipeline
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.
- yesterday First seen · 38 lines · 31 tokens per session scan A 37611f14f4ff
devops is an agent published in the GitHub repository dlupiak/claude-session-dashboard (66 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 314 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
engineering-devops-automator
DevOps自动化工程师，负责CI/CD流水线设计、Docker容器化部署、基础设施即代码(IaC)、监控告警配置，确保项目从构建到部署的全链路自动化.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
ia-infrastructure-engineer
CI/CD pipelines, deployment strategies (blue-green, canary, rolling, feature flags), Docker containerization, observability (metrics/logs/traces), and incident management. Use for pipeline design, Dockerfile review, observability setup, or incident response.
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.