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-summarygit 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-summary)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/requirement-summary"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/requirement-summary/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-summary"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/requirement-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00791 |
| Opus 5 | $0.00034 | $0.00396 |
| Sonnet 5 | $0.00014 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
requirement-summary 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Summary
Overview
Generate structured, bullet-point summaries (5-7 items) from requirement documents that enable teams to quickly grasp core functionality and critical constraints without reading full specifications.
Workflow
1. Analyze the Requirement Document
Read the provided requirement document thoroughly to identify:
- Core functionality and features being requested
- Technical dependencies and system constraints
- Integration points with existing systems
- Critical limitations or blockers
- Success criteria or acceptance conditions
2. Extract Key Information
Focus on information that directly impacts implementation decisions:
- What is being built (features, capabilities, user-facing changes)
- Why it's needed (business value, problem being solved)
- Dependencies (external systems, APIs, data sources, prerequisites)
- Constraints (technical limitations, performance requirements, compliance needs)
- Scope boundaries (what's explicitly excluded or deferred)
3. Structure the Summary
Create a bullet-point list with 5-7 items following this pattern:
**[Category]**: [Concise description]
Recommended categories:
- Core Functionality: Primary features or capabilities
- Key Dependencies: External systems, APIs, or prerequisites
- Technical Constraints: Performance, scalability, or platform limitations
- Integration Points: How this connects with existing systems
- Success Criteria: Measurable outcomes or acceptance conditions
- Out of Scope: Explicitly excluded features or future considerations
4. Apply Clarity Principles
Each bullet point should:
- Start with a bold category label for scannability
- Use active, specific language (avoid vague terms like "improve" or "enhance")
- Include concrete details (numbers, systems, technologies) when available
- Be self-contained and understandable without reading other bullets
- Focus on "what" and "why" rather than "how"
5. Validate Completeness
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 · 92 lines · 69 tokens per session scan A 328e39760b95
requirement-summary is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 69 tokens to every session and 791 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
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.