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.
npx agentmods add commands/alphaaiservice/cortex/env-syncgit clone --depth 1 https://github.com/alphaaiservice/cortexWhat 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 | $0.00036 | $0.04419 |
| Opus 5 | $0.00018 | $0.02210 |
| Sonnet 5 | $0.00007 | $0.00884 |
| Haiku 4.5 | $0.00004 | $0.00442 |
Grade A, and why
env-sync 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 yesterday.
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 — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment Sync & Configuration Management
Action: $ARGUMENTS (default: check)
Parse $ARGUMENTS:
check— Audit all .env files for parity and missing variablesdiff <env1> <env2>— Compare two environment files side by sideencrypt— Encrypt sensitive .env values using age/sopsrotate— Guide through secret rotation for all servicesinit— Generate .env.example and environment templates- No argument =
check
Step 0: Discover Environment Files
echo "=== Environment Files ==="
find . -maxdepth 3 -name ".env*" -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/.venv/*" 2>/dev/null | sort
echo ""
echo "=== Git-tracked .env Files (DANGER) ==="
git ls-files | grep -i '\.env' 2>/dev/null || echo "None (good)"
echo ""
echo "=== .gitignore Coverage ==="
grep -n "env" .gitignore 2>/dev/null || echo "WARNING: No .env entries in .gitignore"
echo ""
echo "=== Docker Compose env_file References ==="
grep -rn "env_file" docker-compose*.yml docker/docker-compose*.yml 2>/dev/null | head -10
echo ""
echo "=== Kubernetes Secrets/ConfigMaps ==="
find . -maxdepth 4 -name "*.yaml" -o -name "*.yml" 2>/dev/null | xargs grep -l "kind: Secret\|kind: ConfigMap" 2>/dev/null | head -10
Build a map of all environment files and their purposes:
.env→ Local development.env.development→ Development overrides.env.staging→ Staging environment.env.production→ Production environment.env.test→ Test environment.env.example→ Template (should be committed)
Step 1: Parse All Environment Files
For each .env* file found, parse into a structured map:
{
"file": ".env",
"variables": {
"DATABASE_URL": { "value": "mysql://...", "has_value": true, "is_secret": true },
"DEBUG": { "value": "true", "has_value": true, "is_secret": false },
...
}
}
Secret detection heuristics — mark as is_secret: true if the variable name contains:
PASSWORD,PASSWD,PWDSECRET,KEY(but notPUBLIC_KEY)TOKEN(but notTOKEN_EXPIRY)API_KEY,APIKEYPRIVATECREDENTIALS,CREDCONNECTION_STRING,DATABASE_URL,MONGO_URI,REDIS_URL
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.
- yesterday First seen · 503 lines · 36 tokens per session scan A 5e8ad043e7ca
env-sync is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 36 tokens to every session and 4,419 once invoked, about $0.0002 per session on Opus 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 commands, from other repositories
_composicion
Protocolo interno compartido para la composición dinámica del equipo de Alfred según tarea, stack y señales runtime.
alfred
Asistente contextual de Alfred Dev. Enruta automáticamente al flujo o comando operativo correcto.
audit
Auditoría completa del proyecto con 4 agentes en paralelo.
feature
Ciclo completo de desarrollo: producto, arquitectura, desarrollo, QA, docs, entrega.
ajustes
Configura Alfred Dev: autonomía, proyecto, Lucius, memoria y personalidad. Antes /alfred-dev:config.
discuss
Refina una idea o feature antes de abrir un flujo completo de implementación.