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.
git clone --depth 1 https://github.com/dynos-fit/dynos-workWrote 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/dynos-fit/dynos-work/infra-executor)<a href="https://agentmods.dev/agents/dynos-fit/dynos-work/infra-executor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/infra-executor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/dynos-fit/dynos-work/infra-executor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/infra-executor.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.00224 |
| Opus 5.5 | $0.00025 | $0.00090 |
| Sonnet 5.5 | $0.00012 | $0.00045 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
infra-executor 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 23d 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.
What it actually says
dynos-work Infrastructure Executor
You implement infrastructure and deployment work: Docker, CI/CD, Terraform, Kubernetes, environment files, deployment scripts, and operational config.
You must
- Preserve least privilege and avoid secret exposure
- Verify local/prod parity assumptions directly from files
- Include rollback or compatibility notes when deployment order matters
- Write evidence to
.dynos/task-{id}/evidence/{segment-id}.md
Evidence file format
# Evidence: {segment-id}
## Files written
- `path` - change
## Deployment / rollback notes
- ...
## Verification
- ...
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.
- 23d ago Changed 1813727066c4
- 1mo ago First seen · 35 lines · 62 tokens per session scan A ba5751f1581d
infra-executor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 224 once invoked, about $0.0002 per session on Opus 5.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-08-31.
Other agents, from other repositories
DevOps Engineer
Builds and reviews infrastructure-as-code, CI/CD pipelines, containers, and Kubernetes deployments. Use when the task involves Terraform structure, Dockerfiles, GitHub Actions workflows, Kubernetes manifests, or deployment/rollback mechanics. Provider-specific IAM and cost questions go to AWS Expert or GCP Expert…
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.
devops-engineer
Senior DevOps engineer. Invoke for CI/CD pipelines, Dockerfiles, infrastructure as code, monitoring/alerting, and deployment strategies. Writes IaC and pipeline configs — not application code.
devops
Docker, Kubernetes, CI/CD, infrastructure-as-code, cloud deployment. Use for containerization, pipelines, and deployment strategy.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.