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 tatagoncalvesof/imperatriz-toolkit --skill skill-historia-metodogit clone --depth 1 https://github.com/tatagoncalvesof/imperatriz-toolkitWrote 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/skill-historia-metodo)<a href="https://agentmods.dev/skills/tatagoncalvesof/imperatriz-toolkit/skill-historia-metodo"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-historia-metodo/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/skill-historia-metodo"><img src="https://agentmods.dev/badge/skills/tatagoncalvesof/imperatriz-toolkit/skill-historia-metodo.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.00106 | $0.01493 |
| Opus 5 | $0.00053 | $0.00746 |
| Sonnet 5 | $0.00021 | $0.00299 |
| Haiku 4.5 | $0.00011 | $0.00149 |
Grade A, and why
skill-historia-metodo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Criador de Historia de Metodo & Especialista
Transformar blueprints tecnicos e informacoes sobre metodos em narrativas de autoridade que estabelecem o especialista como referencia no nicho.
Workflow
Passo 0: Receber o Blueprint
Antes de qualquer coisa, solicitar o blueprint/documento tecnico do metodo. Aceitar:
- Documento PDF/DOCX/TXT com a estrutura do metodo
- Descricao verbal detalhada do metodo
- Framework/modelo visual descrito em texto
- Estrategia comercial documentada
Analisar o blueprint para extrair:
- Estrutura e pilares do metodo
- Diferenciais unicos da abordagem
- Elementos tecnicos que trazem credibilidade
- Linguagem e terminologia propria
Passo 1: Definir Tom e Formato
Perguntar qual tom melhor representa a marca:
| Tom | Ideal para | Caracteristicas |
|---|---|---|
| Profissional & Tecnico | B2B, SaaS, corporativo | Dados, frameworks, ROI |
| Acessivel & Educativo | Cursos, consultoria, mentoria | Didatico, passo-a-passo, exemplos |
| Inspirador & Visionario | Startups, inovacao, disruptivo | Futuro, transformacao, missao |
| Descontraido & Proximo | B2C, lifestyle, creators | Informal, pessoal, autenticidade |
Perguntar formato de saida desejado:
- Historia completa (documento longo)
- Copy para vendas (landing page, emails)
- Roteiro para video/apresentacao
- Carrossel para Instagram
- Pitch para investidores/parceiros
- Todos os formatos
Passo 2: Extrair Narrativa do Blueprint
Analisar o blueprint e preencher a Matriz de Autoridade:
MATRIZ DE AUTORIDADE
1. PROBLEMA CENTRAL — Que dor o metodo resolve?
2. INSIGHT UNICO — O que o especialista percebeu que outros nao veem?
3. PILARES DO METODO — Quais sao os componentes estruturais?
4. MECANISMO UNICO — Como funciona de forma diferente?
5. PROVA DE CONCEITO — Que resultados ja existem?
6. EVOLUCAO — Como o metodo amadureceu?
7. VISAO DE FUTURO — Para onde o metodo esta indo?
Passo 3: Perguntas Estrategicas
Fazer as 7 perguntas fundamentais baseadas na analise do blueprint. Ver references/perguntas-estrategicas.md para templates completos.
What ships with it
4 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 · 127 lines · 106 tokens per session scan A 99368abc320b
skill-historia-metodo is a skill published in the GitHub repository tatagoncalvesof/imperatriz-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 1,493 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-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.