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 requirement-summarizergit 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/requirement-summarizer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/requirement-summarizer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/requirement-summarizer/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/requirement-summarizer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/requirement-summarizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Anti-Refusal · line 213 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00089 | $0.01517 |
| Opus 5 | $0.00044 | $0.00758 |
| Sonnet 5 | $0.00018 | $0.00303 |
| Haiku 4.5 | $0.00009 | $0.00152 |
Grade A, and why
requirement-summarizer 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Summarizer
Overview
Extract and organize the essential information from requirement documents into a structured markdown summary that highlights core features, constraints, and priorities.
Workflow
Follow these steps to summarize requirement documents:
1. Read and Understand the Document
First, read the entire requirement document to understand its structure and content:
- Identify document type (PRD, RFC, user story, business requirement, etc.)
- Note any existing structure (sections, headers, numbering)
- Understand the context and scope of the requirements
2. Extract Key Information
Systematically identify and extract:
Core Features:
- Main functionality being proposed or required
- User-facing capabilities
- System behaviors and interactions
- Integration points with other systems
Constraints:
- Technical limitations or requirements
- Business constraints (budget, timeline, resources)
- Regulatory or compliance requirements
- Compatibility or platform constraints
- Security or privacy requirements
- Performance requirements (latency, throughput, scalability)
Priorities:
- Explicit priority labels (P0, P1, P2, Critical, High, Medium, Low)
- MoSCoW categorization (Must have, Should have, Could have, Won't have)
- MVP vs future phases
- Required vs optional features
- Blocking vs non-blocking items
3. Generate Structured Summary
Create a markdown report with the following structure:
# Requirements Summary: [Document Name]
## Document Metadata
- **Source**: [Document title/filename]
- **Type**: [PRD/RFC/User Story/Business Requirement/etc.]
- **Date Analyzed**: [Current date]
## Executive Summary
[2-3 sentence overview of what this requirement document defines]
## Core Features
### [Feature Category 1]
- **[Feature Name]**: [Brief description]
- Priority: [P0/P1/P2 or Must/Should/Could]
- Notes: [Any relevant context]
### [Feature Category 2]
...
## Constraints
### Technical Constraints
- [Constraint description]
- [Constraint description]
### Business Constraints
- [Constraint description]
- [Constraint description]
### Compliance/Regulatory Constraints
- [Constraint description]
### Performance Constraints
- [Constraint description]
## Priority Breakdown
### Critical/Must-Have (P0)
1. [Feature/requirement]
2. [Feature/requirement]
### High Priority/Should-Have (P1)
1. [Feature/requirement]
2. [Feature/requirement]
### Medium Priority/Could-Have (P2)
1. [Feature/requirement]
2. [Feature/requirement]
### Future/Won't-Have (P3)
1. [Feature/requirement]
## Key Decisions & Open Questions
- **Decision**: [What needs to be decided]
- Options: [If applicable]
- Impact: [Why this matters]
- **Open Question**: [Unclear requirement or missing information]
## Success Criteria
[How will we know this is successful? Metrics, acceptance criteria, or outcomes]
## Dependencies
- [External dependencies or prerequisites]
- [Related systems or teams]
## Timeline & Milestones
- [Key dates if mentioned in requirements]
- [Phase breakdown if applicable]
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 · 215 lines · 89 tokens per session scan A 7bb11b2b874f
requirement-summarizer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,517 once invoked, about $0.0004 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
analysis-to-delivery
A routing guide for turning a new feature request into an analysis and development workflow.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
google-ads-audit
Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.