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 karthikrshet/aiskills --skill requirements-analysisgit clone --depth 1 https://github.com/karthikrshet/aiskillsWrote 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/karthikrshet/aiskills/requirements-analysis)<a href="https://agentmods.dev/skills/karthikrshet/aiskills/requirements-analysis"><img src="https://agentmods.dev/badge/skills/karthikrshet/aiskills/requirements-analysis/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/karthikrshet/aiskills/requirements-analysis"><img src="https://agentmods.dev/badge/skills/karthikrshet/aiskills/requirements-analysis.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.00058 | $0.01622 |
| Opus 5 | $0.00029 | $0.00811 |
| Sonnet 5 | $0.00012 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
requirements-analysis 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 192 lines · 58 tokens per session scan A d54def5f5dec
requirements-analysis is a skill published in the GitHub repository karthikrshet/aiskills (4 stars, last pushed 20d ago), with no licence file. It adds 58 tokens to every session and 1,622 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-08-31.
Other skills, from other repositories
sparc-spec
Use when you need to run SPARC Phase 1 (Specification) for a feature — produces phase1 .md with Functional Requirements, Non-Functional Requirements, and Gherkin acceptance scenarios.
use-case
Produces a complete use case following the Cockburn/RUP format. A use case describes a goal-directed interaction between an actor and the system — capturing not just the happy path, but the extension flows (error, alternative, and exception paths) that user stories typically omit.
requirement-study
Analyze, write, and validate software requirements from any input — conversations, documents, rough notes, or existing specs. Use when someone asks to study requirements, create a PRD, analyze a feature request, extract requirements from a document, or validate completeness of existing requirements. Also triggers on…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…