Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add georgemarmelstein/superjurista-dev/plugin install 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/skills/georgemarmelstein/superjurista-dev/criar-skill)<a href="https://agentmods.dev/skills/georgemarmelstein/superjurista-dev/criar-skill"><img src="https://agentmods.dev/badge/skills/georgemarmelstein/superjurista-dev/criar-skill/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/georgemarmelstein/superjurista-dev/criar-skill"><img src="https://agentmods.dev/badge/skills/georgemarmelstein/superjurista-dev/criar-skill.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.00084 | $0.06287 |
| Opus 5 | $0.00042 | $0.03143 |
| Sonnet 5 | $0.00017 | $0.01257 |
| Haiku 4.5 | $0.00008 | $0.00629 |
Grade A, and why
criar-skill 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.
How it starts
The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<quando_usar> Use quando: - Usuário pede para "criar skill" ou "nova skill" - Usuário quer "transformar workflow em skill" - Usuário menciona "empacotar conhecimento" - Usuário quer "automatizar" um processo repetitivo do Claude - Usuário pede para "melhorar" ou "refatorar" skill existente
<regras_uso> - Subagentes LEEM agents/ diretamente (não recebem cópia) - Orquestrador NÃO executa tarefas dos subagentes - Cada subagente tem contexto ISOLADO - Apenas orquestrador usa TodoWrite </regras_uso>
**Nota sobre Write:** Esta skill usa Write diretamente na Etapa 4 para
criar os arquivos da skill-alvo. Isso é uma exceção justificada ao padrão
"orquestrador não usa Write": aqui o orquestrador É o criador — não há
subagente de escrita porque a montagem do SKILL.md depende do contexto
acumulado das etapas anteriores.
<teste_green_falha> Se o agente ainda VIOLA na fase GREEN (escolhe A com skill): → Skill não está clara o suficiente → Identificar falha específica na instrução → Adicionar regra ou racionalização → Re-testar (máximo 2 tentativas) </teste_green_falha>
<teste_competing_falha> Se o agente CEDE ao pedido contrário na fase COMPETING: → A skill depende do apoio do prompt (falha silenciosa) → Adicionar à a desculpa "o usuário pediu/autorizou" → Re-testar (máximo 2 tentativas) → Persistindo: registrar a pendência no relatório final (não-bloqueante) </teste_competing_falha>
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.
- 9d ago First seen · 617 lines · 84 tokens per session scan A d02815cf9289
criar-skill is a skill published in the GitHub repository georgemarmelstein/superjurista-dev (22 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 6,287 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…