What is requirements_analyzer?

A Vietnamese-language method for analyzing a web page or software module and turning its interface or HTML structure into a requirements document and user stories.

Useful for documenting page layouts, form fields, buttons, alerts, validation rules, happy paths, and edge cases for developers, testers, and quality-assurance work.

It helps teams capture what a running interface actually does, including normal workflows, validation, errors, and unusual cases.

requirements_analyzer — Skill for Claude Code and Codex by anhtester: A Vietnamese-language method for analyzing a web page or…

Install

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.

agentmods

npx agentmods add skills/anhtester/antigravity-testing-kit/requirements_analyzer

Any agent

npx skills add anhtester/antigravity-testing-kit --skill requirements_analyzer

Clone the repo

git clone --depth 1 https://github.com/anhtester/antigravity-testing-kit

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/anhtester/antigravity-testing-kit/requirements_analyzer.svg)](https://agentmods.dev/skills/anhtester/antigravity-testing-kit/requirements_analyzer)

Your own site

<a href="https://agentmods.dev/skills/anhtester/antigravity-testing-kit/requirements_analyzer"><img src="https://agentmods.dev/badge/skills/anhtester/antigravity-testing-kit/requirements_analyzer.svg" alt="Measured on agentmods" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 818 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00030	$0.00818
Opus 5	$0.00015	$0.00409
Sonnet 5	$0.00006	$0.00164
Haiku 4.5	$0.00003	$0.00082

Measured 4d ago against content hash d63657278357, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

requirements_analyzer 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 4d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

requirements_analyzer — 100% identical, 0 lines differ
requirements_analyzer — 100% identical, 0 lines differ

.agent/skills/requirements_analyzer/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kỹ năng Phân tích Yêu cầu (Requirements Analyzer)

Kỹ năng này cung cấp các hướng dẫn chi tiết để AI (Antigravity) có thể chuyển đổi giao diện UI hoặc cấu trúc DOM/HTML của một trang web thành các tài liệu Yêu cầu rõ ràng, chi tiết, phục vụ trực tiếp cho QA, Tester và Developer.

1. Mục tiêu cốt lõi

Xây dựng tài liệu yêu cầu bám sát thực tế hệ thống đang chạy.
Đảm bảo tính nhất quán, tính bao quát cho cả Happy Path và Edge Cases (Trường hợp ngoại lệ/báo lỗi).
Định dạng xuất ra một cách chuyên nghiệp (Sử dụng cấu trúc Artifact).

2. Quy trình trích xuất thông tin

Khi được yêu cầu tạo Requirements từ một trang web:

Phân tích Khung giao diện (Layout Analysis): Xác định các phần Header, Footer, Sidebar, và Nội dung chính (Main Content).
Thu thập Form & Inputs:
- Tìm tất cả các trường nhập liệu (input, select, textarea).
- Ghi nhận thuộc tính type (text, email, password, number), required, maxlength, minlength, pattern.
Thu thập Các nút tương tác (Buttons/Links/Actions):
- Xác định chức năng của từng nút (Save, Submit, Cancel, Delete, Edit).
- Các cảnh báo, thông báo (Alerts, Toasts, Validation Messages) xuất hiện khi tương tác lỗi.
Trích xuất Luồng công việc (Workflows):
- Sự phụ thuộc giữa các thành phần (VD: Nút Submit chỉ enable khi đã tích chọn Checkbox "Tôi đồng ý").

3. Cấu trúc Tài liệu Yêu cầu Đầu ra (Output Format)

Tài liệu cần được format theo Markdown chuyên nghiệp hoặc lưu dưới dạng Artifact (requirements_spec.md).

Nội dung bắt buộc phải có:

3.1. Tổng quan (Overview)

Mô tả tóm tắt tính năng và mục đích của trang web/module.

3.2. Yêu cầu Chức năng (Functional Requirements)

Chia thành các User Stories hoặc Use Cases:

Tên tính năng (Ví dụ: Chức năng Đăng nhập)
Mô tả: "Là một người dùng, tôi muốn... để có thể..."
Tiêu chí chấp nhận (Acceptance Criteria): Ghi rõ các điều kiện cần thỏa mãn.

3.3. Đặc tả Trường Dữ liệu (Field Specifications)

Đây là phần cốt lõi dành cho Automation Tester:

Dùng bảng Markdown (Markdown Table) để liệt kê:
- Tên Trường (Label)
- Loại (Type UI)
- Validation Rules (Bắt buộc / Mặc định / Giới hạn độ dài).
- Ghi chú (Notes).

Read the full file on GitHub · 56 lines

Changes

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.

4d ago First seen · 56 lines · 30 tokens per session scan A d63657278357

Subscribe to this mod's changes

requirements_analyzer is a skill published in the GitHub repository anhtester/antigravity-testing-kit (131 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 818 once invoked, about $0.0002 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.

Planning anhtester antigravity kit test-automation testing-tools

keploy-docs

Guide for contributing to the Keploy documentation site at github.com/keploy/docs. Invoke when a change in keploy/keploy introduces, removes, or alters user-visible behavior (new CLI flag, changed default, new command, new configuration field, new on-disk format) and the docs need to catch up — or when the user asks…

keploy/keploy · 116 tokens

keploy-pr-workflow

Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.

keploy/keploy · 71 tokens

keploy-e2e-test

End-to-end verification of a change to keploy/keploy using keploy's own record/replay against a real sample application. Use whenever the user asks to test a change, verify a fix, prove that a modification works in practice, add e2e coverage for a PR, reproduce a bug against a sample app, or wire a behavior into CI.…

keploy/keploy · 118 tokens

requirements_analyzer