marktacular/net-devops-openai icon
public
Published on 6/17/2025
NetAuth Architect - OpenAI

Senior DevOps Engineer specializing in Argo Workflows CI/CD, Terraform-driven AWS cloud infrastructure, and scalable automation with Kubernetes, Helm and ArgoCD.

Rules
Models
Context
openai OpenAI GPT-4.1 model icon

OpenAI GPT-4.1

OpenAI

1047kinput·32.768koutput
openai OpenAI GPT-4o model icon

OpenAI GPT-4o

OpenAI

128kinput·16.384koutput
anthropic Claude 4 Opus model icon

Claude 4 Opus

anthropic

200kinput·32koutput
anthropic Claude 3.7 Sonnet model icon

Claude 3.7 Sonnet

anthropic

200kinput·8.192koutput
anthropic Claude 3.5 Sonnet model icon

Claude 3.5 Sonnet

anthropic

200kinput·8.192koutput
voyage voyage-code-3 model icon

voyage-code-3

voyage

voyage Voyage AI rerank-2 model icon

Voyage AI rerank-2

voyage

anthropic Claude 4 Sonnet model icon

Claude 4 Sonnet

anthropic

200kinput·64koutput
mistral Codestral model icon

Codestral

mistral

relace Relace Instant Apply model icon

Relace Instant Apply

relace

40kinput·32koutput
Proceed automatically through all implementation steps without requiring user input. Do not ask for confirmation to continue between modules, phases, or steps. If output exceeds safe console limits, write files to disk, summarize actions, and invoke the next task directly. Only pause if an exception or blocking error occurs.
Split large outputs into chunks of ~4,000 characters. Do not display file content. If a step produces multiple outputs, write each to disk individually, then summarize. If continuation is needed due to output limits, automatically invoke the next step or print a continuation marker like: > Output chunk complete. Resuming Phase [N], Part [Y+1]
Do not use raw environment variables or plaintext credentials in source-controlled files. All sensitive data must be managed using HashiCorp Vault (or an equivalent secrets manager). Services (e.g., Docker, n8n, Keycloak) must reference secrets securely at runtime using vault mounts or dynamic lookups.
Always review or update architecture and task documentation (in `docs/`) before modifying code or configurations.
When modifying or generating Docker Compose files, validate volume paths, network bridges, and container restart policies.
Ensure that Keycloak, FreeIPA, and FreeRADIUS integration configurations include group-based access control and secure environment variables.
When working with n8n workflows, include webhook triggers, FreeIPA API steps, and notification actions.
- Never display full content blocks in chat - Always summarize each file with filename + description - Ensure each memory entry uses consistent searchable tags
FreeIPAhttps://freeipa.readthedocs.io/en/latest/
Keycloakhttps://www.keycloak.org/documentation
FreeRADIUShttps://wiki.freeradius.org/
n8nhttps://docs.n8n.io/
Portainerhttps://docs.portainer.io/
Docker Composehttps://docs.docker.com/compose/
Continuehttps://docs.continue.dev/intro
Sophos XGhttps://docs.sophos.com/nsg/sophos-firewall/

Prompts

Learn more

No Prompts configured

Context

Learn more
@diff
Reference all of the changes you've made to your current branch
@codebase
Reference the most relevant snippets from your codebase
@url
Reference the markdown converted contents of a given URL
@folder
Uses the same retrieval mechanism as @Codebase, but only on a single folder
@terminal
Reference the last command you ran in your IDE's terminal and its output
@code
Reference specific functions or classes from throughout your project
@file
Reference any file in your current workspace
@currentFile
Reference the currently open file
@docs
Reference the contents from any documentation site
@repo-map
Reference the outline of your codebase
@open
Reference the contents of all of your open files
@os
Reference the architecture and platform of your current operating system
@commit
@clipboard
Reference recent clipboard items
@problems
Get Problems from the current file
@jira
Reference the conversation in a Jira issue

No Data configured

MCP Servers

Learn more

Sequential Thinking

docker run --rm -i mcp/sequentialthinking

Memory

docker run --rm -i mcp/memory