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 ArabelaTso/Skills-4-SE --skill readme-generatorgit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/readme-generator)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/readme-generator"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/readme-generator/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/arabelatso/skills-4-se/readme-generator"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/readme-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 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 Privilege Escalation · line 129 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 131 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 371 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Privilege Escalation · line 84 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Data Exfiltration · line 190 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00069 | $0.02441 |
| Opus 5.5 | $0.00028 | $0.00976 |
| Sonnet 5.5 | $0.00014 | $0.00488 |
| Haiku 4.5 | $0.00007 | $0.00244 |
Grade B, and why
readme-generator scanned grade B with 2 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Install on Ubuntu: `sudo apt-get install [packages]` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:3000/api/resources \ How it starts
The opening of the file, as written. The whole thing — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Generator
Overview
Analyze a code repository and generate a comprehensive, reproducible README.md that enables users to quickly understand, set up, and use the project with clear instructions and executable examples.
Workflow
1. Analyze Repository Structure
Explore the repository to understand its organization and purpose:
Key files to examine:
package.json,pyproject.toml,Cargo.toml,go.mod- Project metadatarequirements.txt,Pipfile,pom.xml,build.gradle- Dependencies- Main entry points (
main.py,index.js,app.py,cmd/main.go) - Configuration files (
.env.example,config.yaml,settings.py) - Build/task files (
Makefile,package.jsonscripts,tasks.py) - Documentation (
docs/, existingREADME.md,CONTRIBUTING.md)
Information to extract:
- Project name and version
- Programming language(s) and frameworks
- Project type (application, library, CLI tool, research)
- Main features and capabilities
- Dependencies and system requirements
- Entry points and execution methods
2. Generate Project Introduction
Create a clear, compelling introduction section:
Title and badges:
# Project Name
Description (2-4 sentences):
- What the project does
- Why it exists (problem it solves)
- Key features or capabilities
- Target audience or use cases
Example:
## About
[Project Name] is a lightweight web framework for building RESTful APIs with minimal boilerplate. It provides automatic request validation, built-in authentication, and OpenAPI documentation generation. Designed for rapid prototyping and production-ready microservices, it reduces API development time by 50% compared to traditional frameworks.
3. Document Prerequisites
List all system requirements and dependencies:
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.
- 1mo ago First seen · 424 lines · 69 tokens per session scan B 97af31c7abfb
readme-generator is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (259 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 2,441 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
skill-incident-management
Incident response, postmortem facilitation, root cause analysis (RCA), blameless culture, incident timeline documentation, and incident classification. Use when responding to production incidents, writing incident reports, facilitating postmortems, or improving incident response processes.
triage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
skill-knowledge-management
Design docs, RFC (Request for Comments) process, ADR (Architecture Decision Records), code comments (WHY not WHAT), documentation structure, knowledge discovery and search, cross-team communication. Use when documenting decisions, writing design docs, or improving knowledge sharing.
skill-requirements
This skill should be used when the user asks to "write requirements", "create user stories", "define acceptance criteria", "decompose a feature", "analyze an issue", "write a PRD", "create user stories", "acceptance criteria", "roadmap", "feature spec", or discusses "INVEST" criteria, "ambiguity", or "story…