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 lfyxhappy/lfcode --skill requirements-analystgit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/requirements-analyst)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/requirements-analyst"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/requirements-analyst/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/lfyxhappy/lfcode/requirements-analyst"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/requirements-analyst.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.00290 |
| Opus 5.5 | $0.00024 | $0.00116 |
| Sonnet 5.5 | $0.00012 | $0.00058 |
| Haiku 4.5 | $0.00006 | $0.00029 |
Grade A, and why
requirements-analyst 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 1mo 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.
What it actually says
Requirements Analyst
Turn an ambiguous request into a testable, bounded outcome without inventing product decisions.
Workflow
- Establish the requested outcome, intended users, affected systems, and success signal.
- Inspect existing behavior, repository instructions, specifications, issues, telemetry, and tests before treating a statement as a requirement.
- Record functional behavior, non-goals, acceptance criteria, edge cases, compatibility constraints, privacy or security needs, and operational constraints.
- Separate confirmed facts, assumptions, open questions, and alternatives. Ask for a decision when it changes scope, user-facing behavior, data handling, or cost.
- Convert the agreed result into observable acceptance checks and a narrow implementation boundary.
Boundaries
- Keep requirement discovery read-only unless the user explicitly requests a specification or implementation change.
- Do not present inferred preferences, estimates, or undocumented behavior as confirmed requirements.
- Do not collect, expose, or copy sensitive user data merely to make an example concrete.
Completion Check
Report the agreed outcome, acceptance checks, non-goals, unresolved decisions, and evidence used to reach them.
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.
- 1mo ago First seen · 27 lines · 59 tokens per session scan A 312914d51b53
requirements-analyst is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 26d ago), licensed MIT. It adds 59 tokens to every session and 290 once invoked, about $0.0002 per session on Opus 5.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-05.
Other skills, from other repositories
contract
A way to turn agreed design decisions into a formal software design document. The document gives coding agents or other implementers goals, decisions, rules, dependencies, non-goals, and open questions.
note
A lightweight decision log that appends settled decisions and references to a repository file. It records why a decision was made without copying the full source document.
feishu-calendar
A Feishu calendar and scheduling skill. It manages calendars and events and can check when people are available or busy.
feishu-task
A Feishu task-management skill. Feishu, also called Lark, is a work app with tasks and task lists.
retro
A post-run review process for a batch of coding tasks merged into the main branch. It collects repeated failures and turns them into proposed checks, review standards, or task templates.
gateway-stage
Execute a Gateway scheduler stage and return the required structured stage result.