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-4-teste-finalgit 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-4-teste-final)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-4-teste-final"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-4-teste-final/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-4-teste-final"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-4-teste-final.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.00586 |
| Opus 5 | $0.00024 | $0.00293 |
| Sonnet 5 | $0.00010 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
ag-4-teste-final 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
TESTE FINAL — Maquina Autonoma de Teste Final
Invocacao
/teste-final qat ~/Claude/GitHub/raiz-platform
/teste-final ux-qat https://app.example.com
/teste-final benchmark https://app.example.com
/teste-final ciclo ~/Claude/GitHub/raiz-platform
/teste-final e2e ~/Claude/GitHub/raiz-platform
/teste-final --resume
Modos
| Modo | Agent interno | O que faz |
|---|---|---|
| qat | ag-testar-qualidade-qat + ag-criar-cenario-qat | QAT textual PDCA (L1-L4, dual-score) |
| ux-qat | ag-testar-ux-qualidade + ag-criar-cenario-ux-qat + ag-capturar-tela (apps nativos) | UX-QAT visual PDCA (screenshots, AI judge) |
| benchmark | ag-benchmark-qualidade + ag-criar-cenario-benchmark | Benchmark comparativo (dual-run, parity index) |
| ciclo | ag-ciclo-testes | Test-fix-retest completo (max 3 ciclos) |
| e2e | ag-testar-e2e-batch | E2E em batches com auto-fix |
Regra PDF → Markdown (obrigatoria — economia de tokens)
Qualquer PDF consumido por esta machine DEVE ser convertido ANTES via markitdown:
bash ~/Claude/.claude/scripts/pdf2md.sh <arquivo.pdf> → Read/Grep no .md gerado (cache automatico).
NUNCA Read direto de .pdf para extrair texto. Excecao visual (layout/slides): converter primeiro, Read multimodal depois. Enforcement: hook pdf-read-guard.sh. Detalhes: .claude/rules/pdf-markitdown.md.
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 · 42 lines · 48 tokens per session scan A 5c774ef7a556
ag-4-teste-final 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 586 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
figma-to-react-workflow
Orchestrates end-to-end Figma-to-React conversion pipeline with enforced TDD, automated pixel-diff visual QA, E2E testing, and app-type awareness (web apps, Chrome extensions, PWAs). Keywords: Figma to React, design tokens, autonomous component generation, Figma conversion, Tailwind config, component library, TDD…
react-testing-workflows
Testing strategy and execution for React applications. Covers Vitest configuration, React Testing Library patterns, custom hook testing, Playwright E2E, Storybook stories and play functions, and coverage reporting. Keywords: test, vitest, testing library, playwright, storybook, coverage, unit test, integration test…
e2e-test-generator
Generates Playwright E2E tests from build-spec.json with app-type-aware templates for web apps, Chrome extensions, and PWAs. Reads e2e flows from the build spec and produces runnable test files. Keywords: E2E tests, Playwright, end-to-end testing, chrome extension testing, PWA testing, integration tests, browser…
ui-test
Runs UI tests described in plain English by driving real Chrome via the Claude-in-Chrome extension. Covers end-to-end flows (clicks, forms, assertions), visual checks (screenshot + optional baseline diff), accessibility (axe-core), performance (Web Vitals + light Lighthouse-style metrics), and an interactive --debug…
audit-ui-e2e
Runs a beginner-mind end-to-end UI audit of any running app — local dev server, staging, production, or a specific URL. Drives Chrome through every interactive element on the target surface, collects structured findings (severity, category, where, symptom, impact, repro, triage), and hands the result off to…
capture-screens
Automatically navigates a web app using Playwright MCP and captures context-aware named screenshots at each product feature state. Names each file semantically based on context (e.g., checkout-payment-form-filled.png). Outputs a manifest.json mapping filenames to descriptions and a summary report. Use when documenting…