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 agentmods add skills/hellotern/sextant/refine-requirementsnpx skills add hellotern/Sextant --skill refine-requirementsgit clone --depth 1 https://github.com/hellotern/SextantWrote 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/hellotern/sextant/refine-requirements)<a href="https://agentmods.dev/skills/hellotern/sextant/refine-requirements"><img src="https://agentmods.dev/badge/skills/hellotern/sextant/refine-requirements.svg" alt="Measured on agentmods" 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 | $0.00122 | $0.02401 |
| Opus 5 | $0.00061 | $0.01201 |
| Sonnet 5 | $0.00024 | $0.00480 |
| Haiku 4.5 | $0.00012 | $0.00240 |
Grade A, and why
refine-requirements 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 5d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!../principles/SKILL_BODY.md
!../tool-gitnexus/SKILL_BODY.md
Requirements Analysis and Refinement Workflow
Core Principle
Requirements are the source of code — when the source is vague, downstream must be chaotic. The goal of requirements refinement is not to produce perfect documentation, but to eliminate ambiguity, discover contradictions, and complete boundary conditions before writing code, so that "need to come back and ask" during development approaches zero.
When to Trigger This Workflow
Guard: Enter this workflow when 🔴 red ambiguities exist (gaps that would invalidate or fundamentally redirect implementation), or when the user explicitly requests requirements decomposition or feasibility assessment ("break this down", "is this feasible", "help me plan"). If the requirement is clear and no decomposition is requested, skip directly to
sextant:add-feature.
| Trigger Signal | Description |
|---|---|
| Feature requirement has 🔴 red ambiguities (undefined scope, conflicting behavior, unclear ownership) | "Support multiple formats" — which formats? async or sync? who calls this? |
| Requirement description has obvious undefined behavior or missing error paths | Success case described but failure case absent |
| User asks to evaluate feasibility before committing to implementation | "Can this be done? How complex is it?" |
| User asks to break down a vague idea into actionable tasks | "Help me break down this requirement" |
| Requirement gaps discovered mid-development that block progress | "This scenario wasn't considered before" |
Complete Execution Workflow
Step 1: Parse the Original Requirement
Translate the user's natural language requirement into a structured description.
─── Requirement Elements Checklist ──────────────────
Target user: <Who uses this feature?>
Core action: <What operation does the user need to complete?>
Expected result: <What is the system state/output after the operation?>
Trigger condition: <Under what circumstances is this feature triggered?>
Success criteria: <What counts as "done"? Specific verifiable conditions>
─────────────────────────────────────────────────────
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.
- 5d ago First seen · 255 lines · 122 tokens per session scan A 066a3890b1b1
refine-requirements is a skill published in the GitHub repository hellotern/Sextant (15 stars, last pushed 5mo ago), licensed MIT. It adds 122 tokens to every session and 2,401 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-08-30.
Other skills, from other repositories
iflytek-text-proofread
Proofread Chinese text using iFlytek's Official Document Proofreading API (公文校对). Detects 27 types of errors across three categories.
iflytek-image-understanding
Use when user asks to analyze an image, describe image contents, or answer questions about a picture. iFlytek Image Understanding (图片理解) — analyze and answer questions about images using Spark Vision model. WebSocket API, pure Python stdlib, no pip dependencies.
iflytek-contract-intelligence-review
Use when user asks to review contracts, detect contract risks, or perform compliance checks. 合同智能审核 - 对合同扫描件、图片合同、双语合同进行完整审核。 覆盖 OCR 识别、条款分析、风险检测、合规校对、翻译摘要全流程。 适用于法务审核、采购合同审查、供应链合规检查等场景。 关键词：合同审核、风险检测、条款分析、合规校对、contract review、risk detection。.
file-upload-media-expert
Expert guide for file uploads (S3, R2, Supabase Storage), presigned URLs, image/video processing, CDN optimization, and media pipeline architecture / Panduan ahli untuk upload file (S3, R2, Supabase Storage), presigned URL, pemrosesan gambar/video, optimasi CDN, dan arsitektur pipeline media.
design-system-architect
Expert guide for designing, building, and maintaining scalable UI design systems with design tokens, headless primitives, Material Design 3 (M3), Tailwind v4 @theme, and WCAG 2.2 accessibility.
email-notification-expert
Expert guide for transactional email (Resend, Postmark, SES), React Email templates, in-app notifications, and unified communication pipelines / Panduan ahli untuk email transaksional (Resend, Postmark, SES), template React Email, notifikasi in-app, dan pipeline komunikasi terpadu.