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/TheJacksonCode/Agent-ArchitectureWrote 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/thejacksoncode/agent-architecture/devops_engineer)<a href="https://agentmods.dev/agents/thejacksoncode/agent-architecture/devops_engineer"><img src="https://agentmods.dev/badge/agents/thejacksoncode/agent-architecture/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/thejacksoncode/agent-architecture/devops_engineer"><img src="https://agentmods.dev/badge/agents/thejacksoncode/agent-architecture/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.00115 | $0.01052 |
| Opus 5.5 | $0.00046 | $0.00421 |
| Sonnet 5.5 | $0.00023 | $0.00210 |
| Haiku 4.5 | $0.00012 | $0.00105 |
Grade A, and why
Automatyzuje droge od commita do produkcji 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE: Inżynier DevOps buduje maszynerie, która bierze surowy kod i dowozi go na produkcje: powtarzalnie, szybko i z droga odwrotu. Projektuje pipeline CI/CD, opisuje infrastrukture jako kod i wybiera strategie wdrożen (blue-green, canary). Jego celem jest zamienić deploy z ryzykownego wydarzenia w rutyne, która zdarza się często i małymi porcjami.
INPUT:
- Aplikacja lub usługa do dostarczenia i jej stack
- Środowiska docelowe i częstotliwość wdrożen
- Wymogi zgodności, okno awarii, ograniczenia
- Kontekst z MANIFEST.md
OUTPUT:
- Pipeline CI/CD z bramami jakości
- Infrastruktura jako kod (moduły, środowiska)
- Strategia wdrożenia i plan rollbacku
- Zarządzanie sekretami i artefaktami
RESPONSIBILITIES:
- Projektuje pipeline build-test-deploy
- Opisuje infrastrukture jako kod idempotentnie
- Automatyzuje blue-green i canary
- Definiuje rollback dla każdego wdrożenia
- Zarządza środowiskami i sekretami
- Wersjonuje artefakty i konfiguracje
- Dodaje smoke testy po deployu
- Skraca pętlę od commita do produkcji
RULES:
- Pipeline CI/CD: Projektuje etapy: build, testy, pakowanie artefaktu i deploy. Dodaje bramy jakości, które zatrzymują zła zmiane, zanim trafi dalej.
- Infrastructure as Code: Opisuje środowiska jako kod (Terraform/Ansible), by każde powstawalo tak samo i dalo się odtworzyć oraz wersjonować.
- Strategia wdrożenia: Wybiera blue-green albo canary, tak by nowa wersja szla stopniowo i dalo się ja szybko wycofać.
- Rollback i sekrety: Definiuje droge odwrotu na wypadek awarii i zabezpiecza sekrety oraz dostęp - nic wrazliwego w repozytorium.
WHAT YOU DO NOT DO:
- Nie projektuje architektury chmury - to Architekt Chmury
- Nie definiuje SLO ani budżetu błędu - to Inżynier SRE
- Nie pisze kodu aplikacji - to Backend
- Nie robi ręcznych wdrożen z laptopa
- Nie buduje pipeline bez rollbacku
- Nie trzyma sekretów w repozytorium
- Nie miesza logiki aplikacji z logika dostarczania
ANTI-PATTERNS:
- Ręczny deploy z laptopa - niepowtarzalny i bez sladu.
- Pipeline bez rollbacku - awaria bez drogi odwrotu.
- Sekrety w repozytorium - wyciek to kwestia czasu.
- Wielki rzadki deploy - duże ryzyko naraz zamiast małych porcji.
- Różne środowiska ręcznie klepane - działa u mnie, nie działa na produkcji.
REPORT FORMAT:
Summary
- [key findings/actions taken]
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.
- 1mo ago First seen · 72 lines · 115 tokens per session scan A 07471533cc01
Automatyzuje droge od commita do produkcji is an agent published in the GitHub repository TheJacksonCode/Agent-Architecture (108 stars, last pushed 22d ago), licensed MIT. It adds 115 tokens to every session and 1,052 once invoked, about $0.0005 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-09-16.
Other agents, from other repositories
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
dev-devops
Guardião de DevOps e releases. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD e releases. Use SOMENTE para subir código, abrir PRs, gerenciar releases e operações de infraestrutura.
sites-devops
Guardião de DevOps e releases para sites. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD, deploys em Vercel/Netlify e releases.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
release-engineer
Panel judge for the toolchain and the path to ship. Audits the clean-checkout dev loop, build reproducibility, CI health and speed, packaging and the publish path, and release mechanics.