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.
git clone --depth 1 https://github.com/felvieira/claude-skills-fvWrote 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/commands/felvieira/claude-skills-fv/build)<a href="https://agentmods.dev/commands/felvieira/claude-skills-fv/build"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/build/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/commands/felvieira/claude-skills-fv/build"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/build.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.00017 | $0.00193 |
| Opus 5 | $0.00009 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
build 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
/build — Implementação
Objetivo: Implementar a feature ou fix usando backend e/ou frontend conforme a stack do projeto.
Skills ativadas:
- 03 — Backend Engineer (APIs, contratos, auth, banco)
- 04 — Frontend Engineer (React/Next.js, estado, UI)
Input esperado: Spec ou plan com requisitos claros, arquivos-alvo identificados.
Output esperado: Código implementado, testável, seguindo patterns do projeto.
Policies relevantes:
policies/search-first.md— pesquisar codebase antes de implementarpolicies/anti-rationalization.md— não racionalizar atalhospolicies/stack-flexibility.md— respeitar stack existente
Uso: /build [descrição do que implementar ou referência ao plan]
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 · 23 lines · 17 tokens per session scan A 0616da231454
build is a command published in the GitHub repository felvieira/claude-skills-fv (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 17 tokens to every session and 193 once invoked, about $0.0001 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 commands, from other repositories
rpc-client
Generate type-safe RPC client from Hono server routes.
azure-dotnet-webapp:webapp-setup
Interactive setup wizard for ASP.NET Core Web API or Blazor projects on Azure — selects project type, auth, database, and Graph integration; scaffolds the full project structure with compilable stubs; and verifies the build.
integrate
Integrate an API from a product manager's spec into the frontend with full surface mapping, modular SOLID-compliant API layer, and integration testing.
frappe-fullstack
Invoke multiple Frappe agents in parallel for full-stack development - coordinates backend, frontend, and architecture agents for complete feature implementation.
add-seo
Add comprehensive SEO to a page using Next.js 15 Metadata API.
add-table
Create advanced data table component with rich features. Implement column sorting (ascending/descending) with multi-column support. Add pagination with page size selector and jump to page. Implement client-side and server-side filtering. Add column visibility toggle with saved preferences. Implement row selection with…