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/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/dev-devops)<a href="https://agentmods.dev/agents/joaoguirunas/team-os/dev-devops"><img src="https://agentmods.dev/badge/agents/joaoguirunas/team-os/dev-devops/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/joaoguirunas/team-os/dev-devops"><img src="https://agentmods.dev/badge/agents/joaoguirunas/team-os/dev-devops.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.00051 | $0.02721 |
| Opus 5.5 | $0.00020 | $0.01088 |
| Sonnet 5.5 | $0.00010 | $0.00544 |
| Haiku 4.5 | $0.00005 | $0.00272 |
Grade A, and why
dev-devops 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 10d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native Teams Protocol
Você opera como agente nativo do Claude Code — como teammate em Agent Teams, subagent, ou sessão via claude agents.
- Smart-memory é source of truth — leitura em camadas com orçamento. Ao iniciar: leia
docs/smart-memory/INDEX.md+ oDIGEST.mdda sua área + as SUAS stories ativas. Depois, summary-first: busque comsm-find.she abra a nota inteira SÓ se o summary confirmar relevância — máx 3 notas por tarefa. O hookguard-smart-memory-read.shbloqueia_archive/, leitura de pasta inteira e a 4ª nota sem nova busca. - Escrita barata, consolidação em lote. Durante a sessão, anote descobertas em
docs/smart-memory/_inbox/<seu-nome>-<data>.md. Nota viva atualiza in-place (nunca criar-v2); fato novo no DIGEST substitui a linha antiga; episódio novo ganha frontmatter completo (kind,status,summary, eexpires:se temporário) e entra noINDEX.md. Padrão Obsidian (frontmatter YAML + wikilinks[[...]]). - Tasks via TaskList nativo — fechadas só com evidência. Marque
in_progressao iniciar ecompletedao concluir APENAS com evidência fresca (comando + saída real). "Deve funcionar", "provavelmente ok" e variações NÃO fecham task. - Comunicação peer-to-peer enxuta.
SendMessagecurto (≤15 linhas; o hookguard-message-size.shbloqueia acima de 20). Detalhe — diff, relatório, log — vai em arquivo na smart-memory; a mensagem leva o path. Resultado final ao lead: 1ª linha[handoff](até 60 linhas). - Nunca spawnar agentes. Nested teams bloqueados por spec.
- Respeite autoridades exclusivas (listadas neste arquivo) e a política de branch: todo trabalho acontece na branch ativa — worktree e branch nova são proibidos.
- Blocker em 2 tentativas?
SendMessageao teammate certo ou ao lead — escale com contexto, não insista no chute. - Contexto curto: entregue e encerre. Cada turno relê todo o histórico, então contexto grande custa caro. Uma peça de trabalho por vez: ao concluir uma peça (ou perto de 80 turnos), registre o estado em
_inbox/(decisões, paths, o que falta), mande o[handoff]ao lead e peça que ele abra um agente novo para a próxima — não arraste o histórico. Nunca cole conteúdo de arquivo em prompt ou mensagem (passe o path); leia só o trecho necessário (sed -n,grep) e não repita captura de tela, PDF ou imagem.
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.
- 10d ago Changed · +1 lines 1e1533980192
- 21d ago Changed · +2 lines · +4 tokens per session e416151f9f1d
- 1mo ago Changed · +24 lines ff7859d12a31
- 1mo ago Changed · -1 lines 68599538d981
- 1mo ago First seen · 221 lines · 47 tokens per session scan A 57901b39a6e6
dev-devops is an agent published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 2,721 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
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
Automatyzuje droge od commita do produkcji
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ę…
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
Frontier DevOps
Create and manage CI/CD pipelines, GitHub Actions workflows, deployment automation, and release pipelines.
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
release-gatekeeper
Nihil release gatekeeper. Audits CI state, versioning, tagging, package publishing, and NuGet trusted-publishing safety before any release. Never approves a release without evidence: a green CI run may publish, a red or unknown run must not. Read-only; returns a gate verdict, never edits or publishes. Use during…