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 pedroiff0/awesome-skills --skill readme-templategit clone --depth 1 https://github.com/pedroiff0/awesome-skillsWrote 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/pedroiff0/awesome-skills/readme-template)<a href="https://agentmods.dev/skills/pedroiff0/awesome-skills/readme-template"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/readme-template/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/pedroiff0/awesome-skills/readme-template"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/readme-template.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.00072 | $0.02464 |
| Opus 5 | $0.00036 | $0.01232 |
| Sonnet 5 | $0.00014 | $0.00493 |
| Haiku 4.5 | $0.00007 | $0.00246 |
Grade A, and why
readme-template scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. `curl -s -o /dev/null -w "%{http_code}\n" <star-history-url>` → expect 200. How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Template — professional repo standard
Build a professional, rich README for any repository. Combines the financas-app structure with RepoActivity sections (Star History, badges) and the pedroiff0 profile GIF footer.
Trigger
User asks to "create a README", "write a README for repo X", "rewrite my README", "make a professional README", or any task that produces a README.md for a repo.
Source examples
- financas-app README (
financas-app/README.md): hero logo, screenshots grid, index, modules table, stack table, features list, demo, install, config, docker, tests, security, structure, docs, roadmap, contribute, license, author. - Awesome Credential-Verification-Platform (
ishandutta2007/...): centered banner + shields badges, overview, table of contents, comparative tables, how-to-contribute, star history chart, disclaimer — the "RepoActivity" sections. - Profile GIF:
https://raw.githubusercontent.com/pedroiff0/pedroiff0/main/assets/pedroiff0.gif
Anatomy of the README
1. Header (centered)
<div align="center">
<img src="PATH_TO_LOGO" alt="Project Logo" width="120" height="120"/>
> One-line tagline describing the project.
</div>
2. Badges (shields.io — centered, right after header)
Row of flat-square or for-the-badge shields:
- License
- Stars / Forks
- PRs welcome
- Version / Release
- Build status (if CI on)
- Follow / social
<a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square" alt="License"/></a>
<a href="stargazers"><img src="https://img.shields.io/github/stars/OWNER/REPO?style=flat-square&color=gold" alt="Stars"/></a>
3. Screenshots / Demo GIF
<div align="center">
**Tour / Demo**
<img src="docs/assets/demo-tour.gif" alt="Demo" width="900"/>
</div>
4. Table of Contents
- O que é / About
- Módulos / Features
- Stack Técnica
- Funcionalidades
- Demo
- Instalação / Quick Start
- Configuração
- Docker (if applicable)
- Testes
- Segurança / Security
- Estrutura do Projeto
- Documentação
- Roadmap
- Contribuição
- Licença
- Autor
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.
- 10d ago First seen · 245 lines · 72 tokens per session scan A 1464d8eaf596
readme-template is a skill published in the GitHub repository pedroiff0/awesome-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 2,464 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
review-test-refactoring
Review PyTorch test refactoring for correctness and completeness against the decoupling standards defined in the refactor-test-decoupling skill. Accepts a test file path (whole-file review), a PR URL, a git diff, or a branch name. Use this when asked to review a test refactoring PR, check a test decoupling change…
accessibility-testing-best-practices
Use when applying accessibility testing best practices.
accessibility-testing-implementation
Use when applying accessibility testing implementation.
accessibility-testing-axe
Use when testing accessibility with axe.
specification-compliance-review
Use this skill when an implementation is described as partial, passing, or complete and the task is to determine whether it actually satisfies an explicit specification. This is not a generic code review and not a re-run of the test suite. The central question is: does every normative requirement have both a correct…
dx-roaster
Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked…