Borrowing it
Nothing to install: this file belongs to gabrielzucco/cerebro-inevita. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gabrielzucco/cerebro-inevita/main/.agents/skills/sistematizar/SKILL.mdgit clone --depth 1 https://github.com/gabrielzucco/cerebro-inevitaWrote 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/gabrielzucco/cerebro-inevita/sistematizar)<a href="https://agentmods.dev/skills/gabrielzucco/cerebro-inevita/sistematizar"><img src="https://agentmods.dev/badge/skills/gabrielzucco/cerebro-inevita/sistematizar/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/gabrielzucco/cerebro-inevita/sistematizar"><img src="https://agentmods.dev/badge/skills/gabrielzucco/cerebro-inevita/sistematizar.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.00059 | $0.01193 |
| Opus 5 | $0.00030 | $0.00596 |
| Sonnet 5 | $0.00012 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
sistematizar 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sistematizar — trabalho real vira Sistema proprietário
Resultado
Deixe um Sistema configuring em sistemas/outros-instalados/<system-id>/, registrado no control
plane e pronto para o primeiro /operar. Não entregue só mapa, prompt, automação ou pasta de
templates.
O caminho normal é:
Cérebro Base T4 → resultado confirmado → caso real observado → contrato aprovado → pacote local → primeiro run
1. Reutilizar antes de perguntar
Leia somente o necessário:
- o último T4 em
.cerebro/concierge-runs/ou o estado ativo do Cérebro Base; meu-negocio/mapa.mde o recorte relevante;- o Architect spec V2 mais recente em
operacao/arquitetura/, quando existir; conexoes/configuradas/fontes.json, sem abrir fontes;- um System Brief ou fio quente ligado ao resultado.
Não repita onboarding geral. Se ainda não há T4, você pode organizar um System Brief proposto,
mas não instalar nem registrar o Sistema. O próximo passo único é terminar /comecar.
2. Fixar o resultado antes das ferramentas
Confirme, nas palavras do dono:
- resultado completo;
- o que não conta como sucesso;
- output verificável;
- dono e decisão que continua humana;
- setpoint ou condição mínima de aceitação.
Se a resposta for “organizar dados”, “usar IA”, “automatizar” ou “conectar sistemas”, continue até aparecer o que melhora em decisão, venda ou entrega.
3. Observar um caso recente
Peça um rastro recente do trabalho e autorização para lê-lo. Use /fonte para tratar somente
até o nível necessário. Reconstrua o caminho atual, inclusive retornos, exceções e compensações
manuais.
Separe:
declared:o que o responsável contou;observed:o que o caso sustenta;gap:o que ainda não está provado.
Registrar fonte ≠ conectar fonte. Não ingira CRM, Drive, WhatsApp ou outro sistema inteiro.
4. Desenhar a versão manual
Leia o schema de comissionamento antes de escrever o spec. Preencha as oito unidades do Sistema e também:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 126 lines · 59 tokens per session scan A 55eda3c3ac55
sistematizar is a skill published in the GitHub repository gabrielzucco/cerebro-inevita (6 stars, last pushed 8d ago), licensed MIT. It adds 59 tokens to every session and 1,193 once invoked, about $0.0003 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 skills, from other repositories
check-docs
Kit-maintainer diagnostic (LOCAL-ONLY, not distributed) that audits the README and docs/ for staleness against the repo's real command/skill/CLI roster, stamped tree, and cross-doc consistency. Read-only; produces a severity-ranked findings report.
review-agent-config
Diagnostic gate that checks CLAUDE.md and AGENTS.md for completeness, consistency, and stale artifacts — run right after /cold-start and before /add-feature. Read-only; produces a findings report.
deep-test
Perform a deep test of the codebase, validating functional smoke tests, claim verification, drift checks, license headers, and placeholder checks. Trigger whenever the user asks to run deep tests, check code health, or perform strict verification.
cold-start
Bootstrap the ai/ knowledge layer for a repo that has none — draft the MODULEMAP, diagrams, and guide docs as [inferred] for a human to audit, touching no source code. Use when the maps are still placeholders or the user asks to cold-start, bootstrap, or onboard a repository.
adversarial-audit
Deep, judgement-based adversarial code audit — hunts for stale cross-references, unescaped interpolation, platform gaps, generated-file ownership conflicts, and cross-module consistency rot that no mechanical check can catch. Read-only; writes a dated findings report.
implement-spec
Implement a spec from ai/lab/specs/ exactly as written — zero design decisions, stop-and-report on any spec-vs-reality conflict, tests are the definition of done. Built for lighter implementation models.