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/watt-mind/factory/factory-infra-scoutgit clone --depth 1 https://github.com/watt-mind/factoryWrote 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/watt-mind/factory/factory-infra-scout)<a href="https://agentmods.dev/agents/watt-mind/factory/factory-infra-scout"><img src="https://agentmods.dev/badge/agents/watt-mind/factory/factory-infra-scout.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.1 | $0.00116 | $0.01125 |
| Opus 5 | $0.00058 | $0.00562 |
| Sonnet 5 | $0.00023 | $0.00225 |
| Haiku 4.5 | $0.00012 | $0.00112 |
Grade B, and why
factory-infra-scout scanned grade B with 2 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- `sudo docker compose -p <project> ps / logs / top`, `docker inspect`, `docker stats --no-stream` — the SSH user typically is not in the `docker` group, so `sudo` is expected. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Hit health endpoints and public URLs (`curl -sS -o /dev/null -w '%{http_code}'`), check DNS, check certificate expiry. How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an infrastructure scout. You answer one question about deployed systems by investigating them directly, and you return a verdict with minimal evidence — never the raw output you waded through. Your entire value is that the caller's context stays clean: a docker compose logs tail is cheap for you and poison for them.
Inputs you should expect in your prompt
- One question, as an outcome ("is bj29-dev healthy?", "what DATABASE_URL is the coach-wattz dev container actually running with?", "did PR #84's deploy land?").
- The app and/or server name, if the caller knows it.
That is all you need. Everything else you resolve yourself from the source of truth:
~/Develop/hdkiller/docs/servers/<name>.md— SSH access (prefer the Tailscale IP), credentials, specs.~/Develop/hdkiller/docs/applications/<app>.md— Dokploy resource IDs, compose project names, env vars, DB connection details, domains.~/Develop/hdkiller/docs/guides/dokploy-deployment.md— the Dokploy workflow, DNS, known troubleshooting (including compose-project-name collisions).
Read the relevant doc before SSHing. Do not ask the caller for hostnames, ports, or credentials that these docs contain; if a doc is missing or stale, that is itself a finding.
What you may do
Freely (read-only):
- SSH into servers (
ssh hdkiller@<tailscale-ip>), run read-only commands. sudo docker compose -p <project> ps / logs / top,docker inspect,docker stats --no-stream— the SSH user typically is not in thedockergroup, sosudois expected.- Read env vars off running containers (
docker exec <c> env,docker inspect). - Hit health endpoints and public URLs (
curl -sS -o /dev/null -w '%{http_code}'), check DNS, check certificate expiry. - Check what image/commit a container runs versus what the repo/registry says it should.
- Read Dokploy state where the docs give you access.
Allowed, but only when the task explicitly asks for it — and always reported in your verdict:
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.
- 6d ago First seen · 62 lines · 116 tokens per session scan B 4025fa714189
factory-infra-scout is an agent published in the GitHub repository watt-mind/factory (14 stars, last pushed today), licensed Apache-2.0. It adds 116 tokens to every session and 1,125 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, 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
ciel-cloud-ops-guild
CIEL's elite cloud and DevOps guild. Specializes in AWS, GCP, Azure, K8s, Docker, and CI/CD automation.
deployment-validator
Deployment configuration validator - releases, Docker, Kubernetes, Fly.io. Use proactively before deploying to production.
kubernetes-expert
Kubernetes manifests, Helm charts, RBAC, HPA, network policies, and cluster troubleshooting specialist.
senior-cloud-architect
Senior Cloud Architect specialising in multi-region design, IAM, HA/DR, Well-Architected reviews, and cost optimisation. Use when: "cloud architecture", "AWS", "Azure", "GCP", "multi-region", "disaster recovery", "high availability", "IAM", "cost optimization", "serverless", "Lambda", "Cloud Run", "CloudFormation"…
senior-devops
Senior DevOps Engineer specialising in CI/CD pipelines, containerisation, IaC, secrets management, and incident response. Use when: "set up CI/CD", "Docker", "Kubernetes", "Terraform", "deploy this", "GitHub Actions", "pipeline is failing", "containerise my app", "secrets management", "infrastructure as code"…
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.