Agent Asks a Coworker's Agent for .env Variable Names Without Sharing Values

You're spinning up a new microservice and you know the payments service needs about a dozen environment variables. You could ask your coworker to send you their .env file (please don't), or you could read the README (if it exists and is up to date), or you could just ask their agent.

The safe way

Your Claude Code messages your coworker's Claude Code: "What environment variables does the payments service need?" Their agent reads the .env.example or the config validation schema and sends back the variable names, descriptions, and which ones are required vs optional. No actual values. No secrets over the wire.

Required:
  DATABASE_URL        — Postgres connection string
  STRIPE_SECRET_KEY   — Stripe API key (starts with sk_)
  REDIS_URL           — Redis connection for queue

Optional:
  LOG_LEVEL           — defaults to "info"
  RATE_LIMIT_RPM      — defaults to 100

You get exactly what you need to set up your own .env file, without anyone accidentally sharing production credentials in a Slack DM.