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 markdown-reportgit 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/markdown-report)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/markdown-report"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/markdown-report/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/markdown-report"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/markdown-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Prompt Injection · line 169 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- 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.00062 | $0.01975 |
| Opus 5 | $0.00031 | $0.00988 |
| Sonnet 5 | $0.00012 | $0.00395 |
| Haiku 4.5 | $0.00006 | $0.00198 |
Grade A, and why
markdown-report 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 8d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Report Skill
Gerar relatorios estruturados e profissionais em Markdown.
Docs Location (OBRIGATORIO)
PROJECT_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
[ "$PROJECT_ROOT" = "$HOME/Claude" ] && { echo "Erro: workspace raiz, nao projeto"; exit 1; }
DEST="$PROJECT_ROOT/docs/{reports|diagnosticos}/<slug>.md"
Decidir entre reports/ (executivo, sumario, sprint review) vs diagnosticos/ (tecnico, RCA, analise de bug).
NUNCA salvar em ~/Claude/docs/ — bloqueado por hook. Detalhes: ~/Claude/.claude/shared/patterns/docs-location.md.
Estrutura Padrao
---
title: "Report Title"
author: "Author Name"
date: "2026-03-26"
version: "1.0"
status: "draft|review|final"
---
# Report Title
> One-line summary of the report purpose.
## Table of Contents
- [Section 1](#section-1)
- [Section 2](#section-2)
- [Appendix](#appendix)
---
## Section 1
Content here.
## Section 2
Content here.
---
## Appendix
Supporting data, references, raw data.
Templates por Tipo
Relatorio Tecnico
# [Titulo] — Technical Report
**Date**: YYYY-MM-DD | **Author**: Name | **Status**: Draft
## Executive Summary
- Key finding 1
- Key finding 2
- Recommendation
## Context
Why this analysis was needed.
## Methodology
How the analysis was conducted.
## Findings
### Finding 1: [Title]
**Severity**: High/Medium/Low
**Impact**: Description
**Evidence**: Data/screenshots
### Finding 2: [Title]
...
## Recommendations
| # | Action | Priority | Effort | Impact |
|---|--------|----------|--------|--------|
| 1 | Do X | P0 | Low | High |
| 2 | Do Y | P1 | Medium | Medium |
## Next Steps
- [ ] Action item 1
- [ ] Action item 2
## References
- [Link 1](url)
- [Link 2](url)
Relatorio Executivo
# [Titulo] — Executive Summary
**Period**: Month YYYY | **Prepared for**: Stakeholder
## Highlights
- Metric 1: **+15%** vs last period
- Metric 2: **3 of 5** milestones completed
- Risk: [brief description]
## Key Metrics
| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| Revenue | $100K | $115K | On Track |
| Users | 1000 | 850 | At Risk |
## Decisions Needed
1. **[Decision 1]**: Options A vs B — recommend A because...
2. **[Decision 2]**: Approve budget for...
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.
- 8d ago First seen · 297 lines · 62 tokens per session scan A 7d6ef57aa2a8
markdown-report is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (19 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,975 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
docs-sync-internal
Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…
lab-report-writer
A writing workflow for producing structured, journal-style laboratory, research, engineering, or competition reports from experiment details and results.
community-profiler
A skill for analyzing technical community chat records from text, screenshots, JSON, or CSV. It creates member profiles, activity assessments, influence rankings, and community-health findings.
svg-flowchart
A tool for turning written steps into a consistent SVG flowchart. SVG is a scalable image format that can be embedded in web pages and documents.
frontend-dataviz
A skill for choosing and creating clear charts from user-provided data, following the Storytelling with Data approach. It matches chart types to tasks such as comparing categories, showing trends, or displaying distributions.
storybook-story-generation
Use after React components are built (Phase 4.5 of the Figma/Canva/screenshot pipeline) or whenever a project needs Storybook coverage — auto-generates .stories.tsx and .mdx docs from components via ts-morph AST parsing, with prop controls, variant stories, action args, and default args. Keywords: Storybook, generate…