Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/tatagoncalvesof/imperatriz-toolkit/mecanismo-unico)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/mecanismo-unico"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/mecanismo-unico/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/tatagoncalvesof/imperatriz-toolkit/mecanismo-unico"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/mecanismo-unico.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.00267 | $0.04528 |
| Opus 5 | $0.00133 | $0.02264 |
| Sonnet 5 | $0.00053 | $0.00906 |
| Haiku 4.5 | $0.00027 | $0.00453 |
Grade A, and why
mecanismo-unico 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 — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mecanismo Unico — Metodo Proprietario Tata Goncalves
Este skill e o motor de criacao e auditoria de mecanismo unico. Em mercado brasileiro estagio 3+ (90% dos nichos), mecanismo unico e o ativo #1 de copy. Sem ele, headline, VSL e funil nao convertem em escala.
Filosofia central
Promessa diz O QUE. Mecanismo diz COMO. No Brasil 2026, so o COMO converte.
Mecanismo unico e o COMO diferente que explica por que teu metodo funciona quando outros falharam. Tres componentes inseparaveis: causa especifica + solucao proprietaria + nome memoravel.
Quando usar
- Tata (ou mentoranda com skill compartilhada) tem oferta mas nao sabe diferenciar
- Tata quer nomear/renomear um metodo existente
- Tata quer auditar se mecanismo atual esta nota 1000
- Tata quer evoluir mecanismo v1 para v2 (reposicionamento)
- Tata quer criar novo angulo pra publico saturado
- Antes de rodar
/headline-imperatriz— mecanismo e pre-requisito em mercado estagio 3+
Regra critica: a diferenca entre USP, Big Idea, Mecanismo e Metodo
- USP = diferencial comercial/marketing
- Big Idea = angulo narrativo central (O QUE)
- Mecanismo Unico = diferencial causal/cientifico (COMO)
- Metodo = sistema completo de entrega
A skill foca em Mecanismo Unico. Se o usuario confundir, esclarecer.
MODOS DE OPERACAO
A skill roda em 4 modos declaraveis:
/mecanismo-unico(padrao) — modo completo: entrevista + 10 candidatos + validacao/mecanismo-unico express— gera 10 candidatos rapido, sem entrevista extensa/mecanismo-unico auditar— audita mecanismo existente contra os 23 criterios/mecanismo-unico mentoria— pedagogico profundo pra mentoranda, explica cada criterio
Se usuario nao declarar modo, perguntar "modo completo, express, auditar ou mentoria?" em tarefas grandes.
PROCESSO — 9 FASES OBRIGATORIAS
FASE 0 — Leitura do contexto existente
Se o usuario mandou copy/VSL/pagina de vendas/briefing, LEIA antes de perguntar.
What ships with it
9 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 · 486 lines · 267 tokens per session scan A be0cad76aaf4
mecanismo-unico is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 267 tokens to every session and 4,528 once invoked, about $0.0013 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
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
feature-dev
Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.