diff --git a/.agent/workflows/push-all.md b/.agent/workflows/push-all.md
new file mode 100644
index 0000000..580ae81
--- /dev/null
+++ b/.agent/workflows/push-all.md
@@ -0,0 +1,43 @@
+---
+description: Security check, commit with sensible message, and push
+---
+
+# Push All Workflow
+
+## Context
+1. Get key git information:
+   - Current branch: `git branch --show-current`
+   - Git status: `git status --short`
+
+## Step 1: Security Check
+Before committing, scan the staged changes for potential secrets or sensitive data:
+- API keys, tokens, or credentials (patterns like `sk-`, `api_key`, `secret`, `password`, `token`, `bearer`)
+- `.env` files or environment variable files with actual values
+- Private keys or certificates
+- Database connection strings with credentials
+- Hardcoded URLs with authentication parameters
+
+Run `git diff --cached` (and `git diff` if you encounter unstaged files that will be added) to inspect what will be committed.
+If you find ANY potential secrets:
+1. STOP immediately
+2. List the specific files and lines containing potential secrets
+3. Do NOT proceed with the commit
+4. Suggest how to fix (use environment variables, add to .gitignore, etc.)
+
+## Step 2: Stage All Changes
+If security check passes, stage all changes.
+// turbo
+Run `git add -A`
+
+## Step 3: Generate Commit Message
+Analyze the changes and create a concise, meaningful commit message that:
+- Summarizes what changed (not how)
+- Uses imperative mood ("Add feature" not "Added feature")
+- Is 50 chars or less for the subject line
+- Includes the standard footer if applicable
+
+Look at recent commits with `git log --oneline -5` to match the repository's commit style.
+
+## Step 4: Commit and Push
+1. Create the commit with the generated message.
+2. Push to the remote repository.