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/estimate-costgit 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.00037 | $0.04130 |
| Opus 5 | $0.00018 | $0.02065 |
| Sonnet 5 | $0.00007 | $0.00826 |
| Haiku 4.5 | $0.00004 | $0.00413 |
Grade A, and why
estimate-cost 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Estimate Cost — Infrastructure & API Cost Projection
Estimate costs for: $ARGUMENTS (default: analyze current project)
Calculate realistic infrastructure, API, and operational costs for features at three scales: Startup (100 users), Growth (10K users), and Scale (100K users). Works for ANY stack.
KEY PRINCIPLE: Use real pricing data, not guesses. Every estimate should reference actual provider pricing tiers. Always show the cheapest viable option alongside the recommended option.
Step 1: Identify Features to Cost
If $ARGUMENTS describes a specific feature:
Parse the feature description and identify all infrastructure components needed.
If $ARGUMENTS is empty (analyze current project):
Scan the codebase to detect all infrastructure dependencies:
# Detect cloud services
grep -ri "aws\|gcp\|azure\|vercel\|netlify\|railway\|render\|fly\.io\|supabase\|firebase\|heroku" . --include="*.json" --include="*.yml" --include="*.yaml" --include="*.toml" --include="*.env*" --include="*.tf" -l 2>/dev/null
# Detect databases
grep -ri "mysql\|postgres\|mongodb\|redis\|sqlite\|dynamodb\|firestore\|supabase" . --include="*.py" --include="*.ts" --include="*.js" --include="*.java" --include="*.json" --include="*.yml" -l 2>/dev/null
# Detect APIs and services
grep -ri "openai\|anthropic\|stripe\|razorpay\|twilio\|sendgrid\|mailgun\|algolia\|pinecone\|qdrant\|weaviate\|elasticsearch\|sentry\|posthog\|datadog\|newrelic" . --include="*.py" --include="*.ts" --include="*.js" --include="*.java" --include="*.json" --include="*.env*" -l 2>/dev/null
# Detect storage
grep -ri "s3\|minio\|cloudinary\|uploadthing\|cloudflare\|r2\|gcs\|blob" . --include="*.py" --include="*.ts" --include="*.js" --include="*.java" --include="*.json" -l 2>/dev/null
Build a component list:
INFRASTRUCTURE COMPONENTS DETECTED
═══════════════════════════════════
1. [Component] — [provider] — [purpose in the app]
2. [Component] — [provider] — [purpose in the app]
...
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 · 345 lines · 37 tokens per session scan A 83a0d023012b
estimate-cost is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 37 tokens to every session and 4,130 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.