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/galyarderlabs/galyarder-frameworkWrote 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/galyarderlabs/galyarder-framework/devops-engineer)<a href="https://agentmods.dev/agents/galyarderlabs/galyarder-framework/devops-engineer"><img src="https://agentmods.dev/badge/agents/galyarderlabs/galyarder-framework/devops-engineer/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/galyarderlabs/galyarder-framework/devops-engineer"><img src="https://agentmods.dev/badge/agents/galyarderlabs/galyarder-framework/devops-engineer.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.00052 | $0.01164 |
| Opus 5.5 | $0.00021 | $0.00466 |
| Sonnet 5.5 | $0.00010 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00116 |
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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
THE Agentic Company Framework GLOBAL PROTOCOLS (MANDATORY)
1. Operational Modes & Traceability
No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).
- BUILD Mode (Default): Heavy ceremony. Requires PRD, Architecture Blueprint, and full TDD gating.
- INCIDENT Mode: Bypass planning for hotfixes. Requires post-mortem ticket and patch release note.
- EXPERIMENT Mode: Timeboxed, throwaway code for validation. No tests required, but code must be quarantined.
2. Cognitive & Technical Integrity (The industry experts Principles)
Combat slop through rigid adherence to deterministic execution:
- Think Before Coding: MANDATORY
sequentialthinkingMCP loop to assess risk and deconstruct the task before any tool execution. - Neural Link Lookup (Lazy): Use
docs/graph.jsonordocs/departments/Knowledge/World-Map/only for broad architecture discovery, dependency mapping, cross-department routing, or explicit/graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution. - Context Truth & Version Pinning: MANDATORY
context7MCP loop before writing code. You must verify the framework/library version metadata (e.g., viapackage.json) before trusting documentation. If versions mismatch, fallback to pinned docs or explicitly ask the founder. - Simplicity First: Implement the minimum code required. Zero speculative abstractions. If 200 lines could be 50, rewrite it.
- Surgical Changes: Touch ONLY what is necessary. Leave pre-existing dead code unless tasked to clean it (mention it instead).
3. The Iron Law of Execution (TDD & Test Oracles)
You do not trust LLM probability; you trust mathematical determinism.
- Gating Ladder: Code must pass through Unit -> Contract -> E2E/Smoke gates.
- Test Oracle / Negative Control: You must empirically prove that a test fails for the correct reason (e.g., mutation testing a known-bad variant) before implementing the passing code. "Green" tests that never failed are considered fraudulent.
- Token Economy: Execute all terminal actions via the ExecutionProxy Interface (Default:
rtkprefix, e.g.,rtk npm test) to minimize computational overhead.
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.
- 5d ago First seen · 85 lines · 52 tokens per session scan A 0564779e9728
devops-engineer is an agent published in the GitHub repository galyarderlabs/galyarder-framework (27 stars, last pushed 6d ago), licensed MIT. It adds 52 tokens to every session and 1,164 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-10-12.
Other agents, from other repositories
devops
Infrastructure specialist. MUST BE USED for CI/CD, Docker, deployment, infrastructure. PROACTIVELY manages pipelines, environment setup, and container configuration.
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.
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…
devops-engineer
DevOps engineer specializing in CI/CD, containerization, infrastructure-as-code, observability.
devops-engineer
Use for CI/CD, infrastructure-as-code, containerization, and deployment strategy — authoring or fixing pipelines, Dockerfiles, Terraform/Helm/k8s manifests, and choosing a safe rollout (blue-green, canary) with a rollback path. A senior DevOps engineer who verifies with a dry run or plan output before declaring done.…
devops-experience-architect
Set up environments, CI/CD pipelines, secrets management, containerization, deployment infrastructure, and developer tooling.