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 board-meetinggit 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/board-meeting)<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/board-meeting"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/board-meeting/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/board-meeting"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/board-meeting.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.00107 | $0.01699 |
| Opus 5 | $0.00053 | $0.00849 |
| Sonnet 5 | $0.00021 | $0.00340 |
| Haiku 4.5 | $0.00011 | $0.00170 |
Grade A, and why
board-meeting 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 12d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocolo de Reunião de Conselho
Deliberação multi-agente estruturada que evita pensamento de grupo, captura visões minoritárias e produz decisões limpas e acionáveis.
Palavras-chave
reunião de conselho, deliberação executiva, decisão estratégica, C-suite, multi-agente, /cs:board, revisão do fundador, extração de decisão, perspectivas independentes
Invocação
/cs:board [tópico] — ex.: /cs:board Devemos expandir para São Paulo no T3?
O Protocolo de 6 Fases
FASE 1: Coleta de Contexto
- Carregue
memory/company-context.md - Carregue
memory/board-meetings/decisions.md(Apenas Camada 2 — nunca transcrições brutas) - Reinicie o estado da sessão — sem contaminação de conversas anteriores
- Apresente a pauta + papéis ativados → aguarde confirmação do fundador
O Chief of Staff seleciona os papéis relevantes com base no tópico (não todos os 9 toda vez):
| Tópico | Ativar |
|---|---|
| Expansão de mercado | CEO, CMO, CFO, CRO, COO |
| Direção de produto | CEO, CPO, CTO, CMO |
| Contratação/org | CEO, CHRO, CFO, COO |
| Precificação | CMO, CFO, CRO, CPO |
| Tecnologia | CTO, CPO, CFO, CISO |
FASE 2: Contribuições Independentes (ISOLADAS)
Sem contaminação cruzada. Cada agente executa antes de ver as saídas dos outros.
Ordem: Pesquisa (se necessário) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO
Técnicas de raciocínio: CEO: Árvore de Pensamento (3 futuros) | CFO: Cadeia de Pensamento (mostre a matemática) | CMO: Recursão de Pensamento (rascunho→crítica→refinamento) | CPO: Primeiros Princípios | CRO: Cadeia de Pensamento (matemática de pipeline) | COO: Passo a Passo (mapa de processo) | CTO: ReAct (pesquisa→analise→aja) | CISO: Baseado em Risco (P×I) | CHRO: Empatia + Dados
Formato de contribuição (máximo 5 pontos-chave, auto-verificados):
## [PAPEL] — [DATA]
Pontos-chave (máximo 5):
• [Achado] — [VERIFIED/ASSUMED] — 🟢/🟡/🔴
• [Achado] — [VERIFIED/ASSUMED] — 🟢/🟡/🔴
Recomendação: [posição clara]
Confiança: Alta / Média / Baixa
Fonte: [de onde vieram os dados]
O que mudaria minha opinião: [condição específica]
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.
- 12d ago First seen · 149 lines · 107 tokens per session scan A 201ca53df436
board-meeting is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 107 tokens to every session and 1,699 once invoked, about $0.0005 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.