company-repo

company-repo is a command for Claude Code from gonzalezpazmonica/pm-workspace. It costs 39 tokens per session (704 once invoked), scanned A, a copy of company-repo, MIT.

A command for creating, connecting, checking, and synchronizing a company Git repository used for shared knowledge, messages, and status. Git is a system for tracking file changes and sharing them between repositories.

In plain words
What is it for?
Use it to initialize the company repository, connect an employee, check synchronization status, or pull and push changes.
Why use it?
It gives a team one defined process for joining the shared repository and keeping local copies synchronized. It also reports unread messages, recent pulls, and conflicts.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions OpenCode.

Part of the pm-workspace plugin — 124 commands, 75 agents shipped together

Good fit Use it to initialize the company repository, connect an employee, check synchronization status, or pull and push changes.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/gonzalezpazmonica/pm-workspace/company-repo
Install

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.

Clone the repo
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspace

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

Wrote 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.

agentmods badge for company-repo

README.md
[![agentmods](https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/company-repo/github.svg)](https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/company-repo)
Your own site
<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/company-repo"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/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.

agentmods 80×15 button for company-repo

Your own site · 80×15
<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/company-repo"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/company-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 704 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 2c8e184cdfcd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 9d 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.

Origin

This is a copy

100% identical to company-repo — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/company-repo.md · 84 lines

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 leer
  • sync — Pull + push con detección de conflictos

Contexto requerido

  1. @.opencode/skills/company-messaging/references/company-savia-config.md — Config Company Savia
  2. .opencode/skills/company-messaging/SKILL.md — Protocolo de mensajería

Pasos de ejecución

Modo create

  1. Mostrar banner: ━━━ 🏢 Company Savia — Crear Repo ━━━
  2. Preguntar: URL del repositorio Git (ej: https://github.com/org/company-savia.git)
  3. Preguntar: Nombre de la organización
  4. Obtener handle del perfil activo (identity.md → name → slugify)
  5. Ejecutar: bash scripts/company-repo.sh create <url> <org> <handle>
  6. Si no hay keypair → preguntar si generar: bash scripts/savia-crypto.sh keygen
  7. Mostrar resultado + banner de finalización

Modo connect

  1. Mostrar banner: ━━━ 🔗 Company Savia — Conectar ━━━
  2. Preguntar: URL del repositorio Git
  3. Obtener handle y nombre del perfil activo
  4. Ejecutar: bash scripts/company-repo.sh connect <url> <handle> <name> <role>
  5. Si no hay keypair → preguntar si generar
  6. Mostrar resultado + banner de finalización

Modo status

  1. Ejecutar: bash scripts/company-repo.sh status
  2. Mostrar resultado formateado

Modo sync

  1. Ejecutar: bash scripts/company-repo.sh sync
  2. 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

  • create requiere permisos de push al repo Git
  • connect requiere que el repo ya exista
  • NUNCA almacenar credenciales Git en el repo de la empresa
  • Privacy check antes de cada sync

Read the full file on GitHub · 84 lines

Changes

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.

  1. 9d ago First seen · 84 lines · 39 tokens per session scan A 2c8e184cdfcd

Subscribe to this mod's changes

company-repo is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), 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. It is 100% identical to company-repo, differing in 0 lines, and is treated as a copy.