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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/gonzalezpazmonica/savia/company-repo)<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/company-repo"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/company-repo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/company-repo"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/company-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00039 | $0.00704 |
| Opus 5 | $0.00019 | $0.00352 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
company-repo 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 6d ago.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- company-repo — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Company Repo
Argumentos: $ARGUMENTS
Uso:
/company-repo create|/company-repo connect|/company-repo status|/company-repo sync
Parámetros
create— CEO/CTO inicializa el repo de la empresa (pide URL git, nombre org)connect— Empleado se une al repo (pide URL git, genera handle del perfil)status— Estado de sincronización, último pull, mensajes sin leersync— Pull + push con detección de conflictos
Contexto requerido
- @.opencode/skills/company-messaging/references/company-savia-config.md — Config Company Savia
.opencode/skills/company-messaging/SKILL.md— Protocolo de mensajería
Pasos de ejecución
Modo create
- Mostrar banner:
━━━ 🏢 Company Savia — Crear Repo ━━━ - Preguntar: URL del repositorio Git (ej:
https://github.com/org/company-savia.git) - Preguntar: Nombre de la organización
- Obtener handle del perfil activo (identity.md → name → slugify)
- Ejecutar:
bash scripts/company-repo.sh create <url> <org> <handle> - Si no hay keypair → preguntar si generar:
bash scripts/savia-crypto.sh keygen - Mostrar resultado + banner de finalización
Modo connect
- Mostrar banner:
━━━ 🔗 Company Savia — Conectar ━━━ - Preguntar: URL del repositorio Git
- Obtener handle y nombre del perfil activo
- Ejecutar:
bash scripts/company-repo.sh connect <url> <handle> <name> <role> - Si no hay keypair → preguntar si generar
- Mostrar resultado + banner de finalización
Modo status
- Ejecutar:
bash scripts/company-repo.sh status - Mostrar resultado formateado
Modo sync
- Ejecutar:
bash scripts/company-repo.sh sync - Mostrar resultado
Voz Savia (humano)
Savia guía el proceso con calidez:
- Create: "Vamos a crear el espacio compartido de tu empresa..."
- Connect: "Te conecto con el equipo..."
Modo agente
status: OK
action: "create|connect|status|sync"
result: {output del script}
Restricciones
createrequiere permisos de push al repo Gitconnectrequiere que el repo ya exista- NUNCA almacenar credenciales Git en el repo de la empresa
- Privacy check antes de cada sync
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.
- 6d ago First seen · 84 lines · 39 tokens per session scan A 2c8e184cdfcd
company-repo is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 704 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-09-06.
Other commands, from other repositories
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
iterate
Execute a single Ralph loop iteration - complete one work unit from tasks.md with proper commits and progress tracking.
weekly-summary
Generate weekly work summary from git activity.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.