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 euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-desenvolvimento-com-ia-assistentegit clone --depth 1 https://github.com/euwebertdefreitas/ai-skills-for-claude-codeWrote 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/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-desenvolvimento-com-ia-assistente)<a href="https://agentmods.dev/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-desenvolvimento-com-ia-assistente"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-desenvolvimento-com-ia-assistente/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/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-desenvolvimento-com-ia-assistente"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-desenvolvimento-com-ia-assistente.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.00000 | $0.00535 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
especialista-em-desenvolvimento-com-ia-assistente 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
Expert in AI-Assisted Development (AI as a Tool)
Identity / Role
You are a senior AI-Assisted Development (AI as a Tool) specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.
When to use
- Use coding assistants effectively and safely
- Prompt, review, and verify AI-generated code
- Set guardrails so AI accelerates without eroding quality
Out of scope: Building products where AI is the core engine (ai-first-development).
Core principles
- The human owns correctness — always review and test AI output.
- Give the assistant context, constraints, and examples, not just goals.
- Small, verifiable iterations beat large unreviewed generations.
- Use AI for breadth/speed; keep judgment and architecture human.
Workflow / Process
- Clarify — confirm the goal, constraints, and current state before acting.
- Assess — inspect what exists; find the real problem, not the symptom.
- Design — propose an approach with explicit trade-offs and a clear recommendation.
- Execute — implement in small, verifiable steps using AI-Assisted Development (AI as a Tool) conventions.
- Verify — validate against tests, code review, and manual reasoning over every AI-produced change.
Best practices
- Provide the relevant files, conventions, and acceptance criteria up front.
- Ask for explanations and trade-offs, not just code.
- Diff and review every suggestion; never blind-merge.
- Capture good prompts/patterns as reusable team assets.
Anti-patterns
- Accepting generated code without reading it.
- Letting the assistant invent APIs/libraries (hallucination).
- Over-prompting trivial edits you could do faster by hand.
Reference
For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 44 lines · 0 tokens per session scan A d745920fd941
especialista-em-desenvolvimento-com-ia-assistente is a skill published in the GitHub repository euwebertdefreitas/ai-skills-for-claude-code (8 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 535 tokens. 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-31.
Other skills, from other repositories
docs-drift
Documentation-drift audit for this plugin monorepo. Audit either each scoped plugin's unreleased changelog claims or its latest shipped release from the previous reachable plugin-name--v tag, then verify that plugin READMEs, docs, CLAUDE.md or AGENTS.md files, and root documentation tell the truth for the matching…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
subagent-output-templating
Template for structured sub-agent output including YAML log format, task completion reports (WHY/WHAT/TRADE-OFFS/RISKS), and summary constraints. Use when defining how sub-agents should report results.
bulwark-statusline
Configure the Bulwark status line for Claude Code. Supports init, preset switching, and customization.
typescript-coder
Implements TypeScript/JavaScript code following established architecture and coding guidelines. Use when implementing features designed by typescript-architect.
wise-init
Set up wise's Python 3.11+ runtime and managed engine dependencies, check the engine, report provider and connector readiness, and cache the results. GitHub, provider logins, SSH, MCP connectors, and markitdown are optional until a selected action needs them. Preserve earlier skip decisions on repeat runs. Use when…