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 fernando-bertholdo/4-successful-AI-life --skill upstreamgit clone --depth 1 https://github.com/fernando-bertholdo/4-successful-AI-lifeWrote 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/fernando-bertholdo/4-successful-ai-life/upstream)<a href="https://agentmods.dev/skills/fernando-bertholdo/4-successful-ai-life/upstream"><img src="https://agentmods.dev/badge/skills/fernando-bertholdo/4-successful-ai-life/upstream/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/fernando-bertholdo/4-successful-ai-life/upstream"><img src="https://agentmods.dev/badge/skills/fernando-bertholdo/4-successful-ai-life/upstream.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.00067 | $0.03006 |
| Opus 5.5 | $0.00027 | $0.01202 |
| Sonnet 5.5 | $0.00013 | $0.00601 |
| Haiku 4.5 | $0.00007 | $0.00301 |
Grade A, and why
enhanced-planning 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 28d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhanced Planning — Guardrails Estruturais para Planos
Standalone usage (fora do tech-product-template)
Este skill nasceu no tech-product-template, que tem um framework de planejamento
(initiatives → milestones/detours). Você não precisa desse framework para usar os guardrails:
- milestone / detour / initiative = a sua unidade de trabalho (uma feature, um épico, um fix).
Onde o skill pede
enhanced-planning MX.X, use qualquer rótulo:enhanced-planning checkout-v2. {{PLANNING_DIR}}= onde você guarda planos. Default sugerido:.planning/(oudocs/plans/). Se o seu projeto não tem esse diretório, salve o plano ao lado do código/PR.- Skills-companion opcionais (
init-milestone,init-detour,validate-dor,validate-dod,archive-initiative) pertencem ao framework de origem. Se você não os tem, ignore os passos que os mencionam — os guardrails funcionam sozinhos. - As referências a
writing-plans(superpowers) e a/codex:rescue(plugin Codex) são reais e recomendadas. - A seção "Mirror Upstream" no fim do arquivo é metadado de manutenção do template — ignore como usuário do plugin.
Regra de Ouro
"Todo plano de implementacao deve ter guardrails completos: checkpoints humanos, risk registry, decision locks, protocolo multi-sessao, e revisao Codex."
Quando Usar
- Antes de criar plano para milestone ou detour
- Quando tarefa tem 3+ PRs/deliverables
- Quando plano abrange multiplas sessoes
- Quando slice toca output visivel ao stakeholder (email, report, dashboard)
- Quando ha risco de drift entre componentes
Quando NAO Usar
- Tarefas simples (1-2 arquivos, <100 linhas)
- Correcoes pontuais sem risco de regressao, que nao alteram o plano
- Exploracao/pesquisa sem deliverable definido
- Quando
writing-plansdo superpowers ja foi invocado e a tarefa e trivial
Parametros
enhanced-planning [milestone-id|detour-name]
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.
- 28d ago Changed · +2 lines d375d7326590
- 1mo ago First seen · 253 lines · 67 tokens per session scan A c111f4ffe280
enhanced-planning is a skill published in the GitHub repository fernando-bertholdo/4-successful-AI-life (2 stars, last pushed 10d ago), licensed MIT. It adds 67 tokens to every session and 3,006 once invoked, about $0.0003 per session on Opus 5.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
example-feature-generator
Generate boilerplate for new features following project conventions. Use when user says "create feature", "add feature", or "new feature scaffolding".
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
agent-flutter-developer
Specialist subagent: Flutter/Dart cross-platform development, Riverpod state management, and platform channels specialist. Use when building Flutter apps, implementing state management, or working with native platform features. Trigger phrases: Flutter, Dart, Riverpod, Bloc, widget, MaterialApp, GoRouter, platform…
content-repurposer
Adapt content across platforms with tone/format shifting — blog to social, long to short, text to visual outline. Use when repurposing content for different channels, audiences, or formats.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.