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-construir-validadogit 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-construir-validado)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-construir-validado"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-construir-validado/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-construir-validado"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-construir-validado.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.00048 | $0.00526 |
| Opus 5 | $0.00024 | $0.00263 |
| Sonnet 5 | $0.00010 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
ag-construir-validado 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.
What it actually says
ag-construir-validado — Builder/Validator Pattern
Implements the builder/validator pattern where implementation and review happen concurrently instead of sequentially.
Invocation
Use the Agent tool with:
subagent_type:general-purposemode:autoprompt: Compose from template below
Prompt Template
Projeto: [CWD]
Scope: [from arguments]
## Pattern: Builder + Validator Concurrent
1. Read task_plan.md to understand what needs to be built
2. Spawn TWO agents in parallel:
**Builder (ag-implementar-codigo)**:
- Agent tool with subagent_type: ag-implementar-codigo
- isolation: worktree
- Implements all items from task_plan.md
- Commits incrementally every 5 actions
**Validator (ag-revisar-codigo)**:
- Agent tool with subagent_type: ag-revisar-codigo
- run_in_background: true
- Reviews code as it's committed
- Reports issues found
3. During build: Builder uses LSP tool (hover/documentSymbol) for instant type validation on modified files — avoids spawning tsc during iterative work
4. After both complete:
- Read validator output
- If issues found: fix them
- Run quality gates: tsc full (`bun run typecheck`) + lint + test (only here, not during build)
- Report final status
Inter-Agent Communication
- Builder uses SendMessage to notify coordinator at key milestones:
- Module complete, blocker found, self-check result
- Validator uses SendMessage to report issues found during review
- Coordinator reads messages and decides: continue, fix, or escalate
Important
- Builder and validator run CONCURRENTLY — this is the key innovation
- Validator reviews code as it appears, not after all code is written
- This reduces cycle time vs sequential build→review
- allowed-tools for coordinator MUST include SendMessage
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 · 67 lines · 48 tokens per session scan A a6121fe3b7ec
ag-construir-validado is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 526 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.