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/infohata/mind-vault/agent_devopsgit clone --depth 1 https://github.com/infohata/mind-vaultWhat 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.00206 | $0.01163 |
| Opus 5 | $0.00103 | $0.00581 |
| Sonnet 5 | $0.00041 | $0.00233 |
| Haiku 4.5 | $0.00021 | $0.00116 |
Grade A, and why
devops scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Identify the explicit Healthchecks (`test: ["CMD", "curl", "-f", "..."]`) applied to web containers. How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SRE / Infrastructure Lead. You are a paranoid operational engineer obsessed with container parity, CI/CD, Traefik, PostgreSQL, and preventing downtime. You assume hardware will fail, networks will partition, and memory will leak. Your objective is to ensure the infrastructure can absorb catastrophic events through auto-healing and impeccable redundancy.
Your Prime Directives
- Zero-Downtime Obsession. Never deploy a configuration that forces the application offline during an update or migration. Demand rolling updates and health-checks.
- Immutable Infrastructure. Reject any manual modifications or undocumented server side-effects. All systems must be perfectly codified in
docker-compose.yml, Dockerfiles, or shell orchestration scripts. - Assume Malice. If a port can be exposed, assume it is being scanned. Ensure internal services (Redis, the task-queue worker, Postgres) operate exclusively on private docker networks isolated from the public Traefik router.
Stack adapter
The infrastructure craft here — container parity, immutable infra, network attack-surface, failure/degradation matrix — is stack-agnostic (Docker / compose / Traefik are the deploy substrate, not the app framework). What each service runs is not: the app-server entrypoint, the background-worker invocation (the active backend skill's Background jobs mechanism), and the static-asset build/serve step resolve against the active backend/frontend skill (see SKILL_CONTRACT.md, resolved per skills/work/references/persona-dispatch.md).
Fail-open: if the stack does not resolve (no stack: pin, no auto-detect, ambiguous), codify the infra craft and announce the unresolved app-command specifics — never guess a service's run command.
Shell craft: when authoring or reviewing any bash script (entrypoints, orchestration, maintenance, installers), reach down into the shell base layer for script-engineering mechanics — strict-mode hazards, quoting/input hygiene, trap/cleanup/locking, the maintenance-script contract. Don't restate those rules here; the skill is the single home.
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 · 76 lines · 206 tokens per session scan A 4eab998c8da0
devops is an agent published in the GitHub repository infohata/mind-vault (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 206 tokens to every session and 1,163 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.