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 skills add ricneves-ai/flowgrammers-skills --skill company-osgit clone --depth 1 https://github.com/ricneves-ai/flowgrammers-skillsWrote 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/skills/ricneves-ai/flowgrammers-skills/company-os)<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/company-os"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/company-os/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/skills/ricneves-ai/flowgrammers-skills/company-os"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/company-os.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.00124 | $0.02990 |
| Opus 5.5 | $0.00050 | $0.01196 |
| Sonnet 5.5 | $0.00025 | $0.00598 |
| Haiku 4.5 | $0.00012 | $0.00299 |
Grade A, and why
company-os 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sistema Operacional da Empresa
O sistema operacional é a coleção de ferramentas, ritmos e acordos que determinam como a empresa funciona. Toda empresa tem um — a maioria simplesmente não sabe qual é. Torná-lo explícito o torna melhorável.
Palavras-chave
sistema operacional, EOS, Entrepreneurial Operating System, Scaling Up, Rockefeller Habits, OKR, Holacracy, reunião L10, rocks, scorecard, gráfico de accountability, lista de problemas, IDS, ritmo de reuniões, planejamento trimestral, scorecard semanal, framework de gestão, ritmo da empresa, traction, Gino Wickman, Verne Harnish
Por Que Isso Importa
A maioria das disfunções operacionais não é um problema de pessoas — é um problema de sistema. Quando:
- Os mesmos problemas recorrem toda semana: sem sistema de resolução de problemas
- Reuniões parecem inúteis: sem ritmo estruturado de reuniões
- Ninguém sabe quem é responsável por quê: sem gráfico de accountability
- Metas trimestrais escorregam: os rocks não são compromissos reais
Corrija o sistema. As pessoas vão operar melhor dentro dele.
Os Seis Componentes Centrais
Todo sistema operacional eficaz tem estes seis, independentemente do framework que você escolher:
1. Gráfico de Accountability
Não é um organograma. Um gráfico de accountability responde: "Quem é responsável por este resultado?"
Distinção-chave: Uma pessoa é responsável por cada função. Múltiplas pessoas podem trabalhar nela. Responsabilidade significa que o dinheiro para com uma pessoa.
Estrutura:
CEO
├── Vendas (CRO/VP de Vendas)
│ ├── Pipeline inbound
│ └── Pipeline outbound
├── Produto e Engenharia (CTO/CPO)
│ ├── Roadmap de produto
│ └── Entrega de engenharia
├── Operações (COO)
│ ├── Sucesso do cliente
│ └── Financeiro e Jurídico
└── Pessoas (CHRO/VP de Pessoas)
├── Recrutamento
└── Operações de pessoas
Regras:
- Sem responsabilidade compartilhada. "Alice e Bob são ambos responsáveis" significa que ninguém é.
- Uma pessoa pode ser responsável por múltiplas cadeiras nos estágios iniciais. Tudo bem. Apenas seja explícito.
- Revise trimestralmente à medida que você escala. A responsabilidade muda conforme a empresa cresce.
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.
- 1mo ago First seen · 239 lines · 124 tokens per session scan A 28788d163a5f
company-os is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (116 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 2,990 once invoked, about $0.0005 per session on Opus 5.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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.