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 agentmods add commands/georgemarmelstein/superjurista-dev/skill-probaticagit clone --depth 1 https://github.com/georgemarmelstein/superjurista-devWrote 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/georgemarmelstein/superjurista-dev/skill-probatica)<a href="https://agentmods.dev/commands/georgemarmelstein/superjurista-dev/skill-probatica"><img src="https://agentmods.dev/badge/commands/georgemarmelstein/superjurista-dev/skill-probatica.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.09559 |
| Opus 5 | $0.00015 | $0.04779 |
| Sonnet 5 | $0.00006 | $0.01912 |
| Haiku 4.5 | $0.00003 | $0.00956 |
Grade A, and why
skill-probatica 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 4d 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 — 850 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<tools_subagentes> | Tool | Função | |------|--------| | Read | Ler prompts e entradas | | Write | Salvar resultados | </tools_subagentes>
<regras_uso> - Subagentes LEEM prompts diretamente (não recebem cópia) - Orquestrador NÃO executa tarefas dos subagentes - Orquestrador NÃO lê o prompt: instrui subagente a ler via Read - Cada subagente tem contexto ISOLADO (não vê conversa anterior) - EXCEÇÃO Etapa 2: Orquestrador LÊ o inventário para fazer triagem (não é tarefa de subagente) </regras_uso>
<sinalizador_ausente> AVISO: Sinalizador não encontrado. -> Regenerar com SUFIXO DE CORREÇÃO específico -> Se falhar 2x -> PARAR e informar usuário </sinalizador_ausente>
<processo_nao_encontrado> Se processo.txt não encontrado em data/sentenca/$NUMERO: -> Verificar em data/decisao/$NUMERO -> Se encontrado, usar como $WORKSPACE -> Se não encontrado em nenhum, PARAR e informar usuário </processo_nao_encontrado>
<limite_tentativas> | Escopo | Limite | |--------|--------| | Por etapa | 2 tentativas | | Total no pipeline | 12 tentativas | </limite_tentativas>
<contratos_dados>
| # | Etapa | Entrada | Saída | Validação |
|---|---|---|---|---|
| 0 | Preparação | $ARGUMENTS | $WORKSPACE, $NUMERO, $PROCESSO | Variáveis extraídas |
| 1 | Inventário | $PROCESSO | $NUMERO-inventario.md | "# INVENTÁRIO PROBATÓRIO" ... "É o que satisfaz inventariar do acervo probatório." |
| 2 | Triagem | inventário | Lista de analistas a ativar | Orquestrador lê inventário e decide |
| 3 | Analistas | $PROCESSO + inventário | $NUMERO-analise-[tipo].md | Sinalizadores de cada analista |
| 4 | Mapeamento | inventário + análises | $NUMERO-mapa-qualidade.md | "# MAPA DE QUALIDADE PROBATÓRIA" ... "Mapa de qualidade probatória concluído." |
| 5 | Lacunas | mapa + inventário | $NUMERO-lacunas.md | "# ANÁLISE DE LACUNAS PROBATÓRIAS" ... "Análise de lacunas probatórias concluída." |
| 6 | Finalização | - | Resumo ao usuário | - |
| </contratos_dados> |
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.
- 4d ago First seen · 850 lines · 30 tokens per session scan A 0f110e3b6c12
skill-probatica is a command published in the GitHub repository georgemarmelstein/superjurista-dev (20 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 9,559 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-08-30.
Other commands, from other repositories
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.