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-enhancergit 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-enhancer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/requirement-enhancer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/requirement-enhancer/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-enhancer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/requirement-enhancer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 14 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00114 | $0.01937 |
| Opus 5 | $0.00057 | $0.00968 |
| Sonnet 5 | $0.00023 | $0.00387 |
| Haiku 4.5 | $0.00011 | $0.00194 |
Grade A, and why
requirement-enhancer 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Enhancer
Transform initial requirements into clear, complete, actionable specifications through iterative analysis and refinement.
Core Principles
Preserve Intent
- Maintain the user's original goals and vision
- Do not change fundamental requirements without confirmation
- Clarify rather than assume
Iterative Refinement
- Analyze → Ask → Refine → Repeat
- Ask targeted questions to fill gaps
- Incorporate user responses progressively
Explicit Over Implicit
- Make assumptions visible with [ASSUMED] or [INFERRED] labels
- Distinguish confirmed facts from educated guesses
- Highlight areas needing clarification
Avoid Over-Specification
- Do not add unnecessary details without user input
- Focus on essential requirements first
- Mark nice-to-have vs. must-have clearly
Enhancement Workflow
1. Initial Analysis
Analyze the requirement across multiple dimensions:
Clarity: Identify vague terms, ambiguous language, undefined metrics Completeness: Find missing functional/non-functional requirements, edge cases Consistency: Detect conflicts, contradictions, terminology issues Feasibility: Note technical concerns, resource constraints Testability: Check for measurable acceptance criteria
2. Identify Issues
Categorize issues by severity:
🔴 Critical: Core functionality undefined, conflicting requirements 🟡 Important: Missing constraints, unclear scope, vague metrics 🟢 Minor: Terminology inconsistencies, formatting issues
3. Formulate Questions
Ask targeted clarification questions:
For ambiguity: "What exactly does [vague term] mean in measurable terms?" For incompleteness: "What should happen when [edge case]?" For conflicts: "How do requirements X and Y work together?" For missing details: "What are the [performance/security/usability] requirements?"
Use the AskUserQuestion tool to present questions clearly.
4. Incorporate Responses
Based on user answers:
- Update requirements with confirmed information
- Add [CONFIRMED] labels to user-provided details
- Keep [ASSUMED] labels for inferences
- Note [INFERRED] for logical deductions
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 288 lines · 114 tokens per session scan A 45ae72f09795
requirement-enhancer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 114 tokens to every session and 1,937 once invoked, about $0.0006 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.