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-referencia-mock-firstgit 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-referencia-mock-first)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-referencia-mock-first"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-referencia-mock-first/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-referencia-mock-first"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-referencia-mock-first.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.00051 | $0.01003 |
| Opus 5 | $0.00026 | $0.00502 |
| Sonnet 5 | $0.00010 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
ag-referencia-mock-first 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 9d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ag-referencia-mock-first — Metodologia Mock-First (Reference Skill)
Quando usar
- Iniciando projeto que integra com API externa (ERP, CRM, legado)
- Planejando migração de mock data para API real
- Revisando se o protótipo está pronto para integração
- Definindo adapters, providers ou feature flags
As 6 Fases
Fase 1 — Estrutura e Mock Data
- Definir módulos e rotas (lista completa)
- Criar mock data com seed determinístico (reproduzível, 100-500 registros)
- Criar mock store mutável (Map in-memory para write-back)
- Criar schemas Zod para cada server action
- Volumetria real declarada: 2 camadas desacopladas — número real publicado (constante
VOLUMETRIA_REALdocumentada, com fonte) vs amostra gerada para popular a UI (teto ~5k registros; acima do teto, usar amostra % com racional explícito de por que representa o todo). KPI/contador na UI mostra sempre o número real publicado — nuncadataset.lengthdo mock.
Fase 2 — UI Completa com Mock
- Construir todas as páginas consumindo mocks diretamente
- Padronizar design system (KPI Card, tabelas, cores, filtros)
- Server Actions com
safeAction(schema, data, handler)pattern - ActionResult padronizado:
{ success, data }|{ success: false, error }
Fase 3 — Auditoria UX
- Capturar screenshots de todas as rotas via Playwright CLI
- Estados universais: cada rota também capturada em
?estado=loading,?estado=vazio,?estado=erro(hookuseEstadoDemo, gate de ambiente) — mecanismo padrão para provar estados sem backend - Análise visual por critério (hierarquia, densidade, consistência, cores, empty states)
- Classificar problemas (P0 dados, P1 visual, P2 feature, P3 polish)
- Corrigir em sprints por prioridade
Fase 4 — Preparação para Integração
- Error boundaries (
error.tsx) em cada route group - Loading states (
loading.tsx) com skeleton - API Contracts (interfaces TypeScript do shape externo)
- Adapters (ExternalType → AppType)
- Providers (flag → mock | API real)
- Feature Flags (toggle mock/real por módulo)
- REST/SOAP clients com gotchas documentadas no código
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.
- 9d ago First seen · 86 lines · 51 tokens per session scan A d760bdc48b94
ag-referencia-mock-first is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 1,003 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
trigger-realtime-and-frontend
Trigger.dev client/frontend surface: subscribe to runs in realtime (runs.subscribeToRun and the @trigger.dev/react-hooks hook useRealtimeRun), consume metadata and AI/text streams in React (useRealtimeStream), trigger tasks from the browser (useTaskTrigger, useRealtimeTaskTrigger), and mint scoped frontend credentials…
supabase-nextjs
Next.js with Supabase and Drizzle ORM.
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…