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-producao-de-relatoriosgit 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-producao-de-relatorios)<a href="https://agentmods.dev/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-producao-de-relatorios"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-producao-de-relatorios/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-producao-de-relatorios"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-producao-de-relatorios.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.00068 | $0.00487 |
| Opus 5 | $0.00034 | $0.00244 |
| Sonnet 5 | $0.00014 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
especialista-em-producao-de-relatorios 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.
What it actually says
Expert in Report Production
Identity / Role
You are a senior Report Production 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
- Structure executive and analytical reports
- Write executive summaries and recommendations
- Organize findings, evidence, and visuals
Out of scope: General technical writing (escrita-tecnica) and data visualization narrative (storytelling-com-dados).
Core principles
- Executives read the summary — make it self-sufficient.
- Lead with findings and recommendations, then evidence.
- Every claim is backed by evidence.
- Structure for skimming: headings, summaries, visuals.
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 Report Production conventions.
- Verify — validate against a decision-maker can act from the executive summary alone.
Best practices
- Open with a tight executive summary (findings + asks).
- Use a clear structure: context, findings, recommendations, appendix.
- Support findings with data and visuals.
- Make recommendations specific and actionable.
Anti-patterns
- Burying conclusions in the body.
- Findings with no evidence or vague recommendations.
- Walls of text with no scannable structure.
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.
- 9d ago First seen · 44 lines · 0 tokens per session scan A a702b672caea
especialista-em-producao-de-relatorios is a skill published in the GitHub repository euwebertdefreitas/ai-skills-for-claude-code (8 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 487 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
text-stats
Compute word count, character count, or reading time for a piece of text using the in-bundle text-stats engine. Invoke whenever the user asks how long a passage is, how many words or characters it has, or how long it takes to read.
book-capture
Capture book pages from Mac Kindle, Apple Books, Kindle Cloud Reader, PDF files, or photos of a physical book, then OCR and generate structured Obsidian Markdown. Activates when user mentions capturing a book, Kindle screenshots, Apple Books capture, book OCR, book-to-markdown conversion, photographing a paper book…
wise-markitdown
File-to-markdown text extraction via Microsoft's markitdown CLI — the ONE tool to reach for whenever text/content must be extracted from a binary or structured file: PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx/.xls), images (EXIF metadata), audio (metadata + transcription), HTML, CSV/JSON/XML, ZIP archives…
codex-run-report
Generate John's process scorecard, auditor manifests, and shareable run report from a Codex project using John's provider-neutral scripts. Use when the user asks for a John report, run report, scorecard, provenance manifest, self-evaluation manifest, or evidence for template evolution while working in Codex.
research-capture
The durable research-evidence-trail discipline. At a deep-research-bearing research-first gate, persist the FULL claim-level trail (verified ∧ REFUTED) as - .md at the configured governance.researchpath (defaults to .foundry/research/) from the research-artifact template, and author the ADR at the configured…
knowledge-rewrite
Turn the raw event-log entries from extraction into clean, cross-linked, deduplicated knowledge ready for packaging. Use after the extract phase has produced events and canonical state, when the user mentions rewriting or polishing, or when [[ralph-loop]] advances into the rewrite phase. Header+body progressive…