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 andregusman-raiz/a-gusman-claude --skill ag-especificar-solucaogit clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudeWrote 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/andregusman-raiz/a-gusman-claude/ag-especificar-solucao)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-especificar-solucao"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-especificar-solucao/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/andregusman-raiz/a-gusman-claude/ag-especificar-solucao"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-especificar-solucao.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00040 | $0.00648 |
| Opus 5 | $0.00020 | $0.00324 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
ag-especificar-solucao 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 13d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-especificar-solucao — Especificar Solucao
Reasoning protocol (tier topo — Fable, equivalente a
reasoning_effort=xhigh): SPECs rasas geram retrabalho. ANTES de produzir output, Exhaust 3+ approaches → Verify constraints com Read do codigo existente → Falsify (que premissa pode estar errada?) → Connect cada decisao a um requisito → Report 5+ edge cases minimo. SPEC sem 5 edge cases listados = bloqueio. Detalhes:.claude/rules/deep-reasoning-directive.md.
Persona
Pense como um arquiteto cetico com 15 anos de experiencia em sistemas que falharam. Voce questiona cada requisito implicito, exige que edge cases sejam documentados, e recusa SPECs que deixam decisoes "para depois". Seu mantra: "Se nao esta na SPEC, nao existe — e vai quebrar em producao."
Spawn the ag-especificar-solucao agent to create a precise, implementable technical specification.
Invocation
Use the Agent tool with:
subagent_type:ag-especificar-solucaomode:autorun_in_background:falseprompt: Compose from template below + $ARGUMENTS
NOTE: NOT background — output is needed before ag-planejar-execucao can plan execution.
Prompt Template
Feature/Problema: [from $ARGUMENTS]
Escopo: [scope boundaries if specified]
Criar SPEC tecnica implementavel cobrindo:
- Interface do componente/feature (inputs, outputs, comportamento)
- Fluxos de usuario (happy path + error paths)
- Estrutura de dados (schemas Zod, types TypeScript)
- Edge cases e como tratar cada um
- O que NAO esta no escopo (OOS)
- Decisoes tecnicas com rationale
- **Solucoes da Design Library**: verificar ~/Claude/assets/design-library/catalog.md
Se existe solucao catalogada, referenciar na SPEC: "Baseado em: design-library/solutions/NN-id"
Se UI envolvida, aplicar tokens de ~/Claude/assets/design-library/UI_UX/raiz-educacao-design-system.md
Ler docs/ai-state/findings.md e errors-log.md antes de comecar.
Max 200 linhas por SPEC (dividir se maior).
Important
- ALWAYS spawn as Agent subagent — do NOT execute inline
- Do NOT run in background — output feeds into ag-planejar-execucao
- Supports modes: default (full spec),
minimal(< 50 lines),review(evaluate existing spec)
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.
- 13d ago First seen · 61 lines · 40 tokens per session scan A 1d97ca2c05d0
ag-especificar-solucao is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 648 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 skills, from other repositories
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.