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/leifericf/agentic-sdk/define-requirementsnpx skills add leifericf/agentic-sdk --skill define-requirementsgit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/define-requirements)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/define-requirements"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/define-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.00011 | $0.00356 |
| Opus 5 | $0.00005 | $0.00178 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
define-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 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.
What it actually says
define-requirements
Define WHAT must be built as testable, scoped requirements. No tech stack, architecture, timelines, or estimates.
Procedure
- Read
project-meta.md,problem-description.md, andopen-questions.md. If a prerequisite is missing, returnblocked: <which artifact>. - Surface any
[Blocking]items affectingproduct-requirements.mdand resolve them first. - Clarify ambiguities, at most three questions per turn: contradictions
between goals and constraints, implicit assumptions, acceptance criteria
made concrete and testable. Park unclear requirements in
open-questions.mdas- [ ] [Affects: product-requirements.md] <question> (Answer: TBD). - Iterate until scope is crisp and confirmed. Shape requirements around the smallest valuable increments.
- Write
~/.agentic-sdk/<project>/artifacts/planning/product-requirements.mdwith: Metadata, Problem Statement, Goals, Non-Goals, Users, Scope, Functional Requirements (each with priority and acceptance criteria), Non-Functional Requirements, Workflows, Success Criteria, Assumptions. Keep open questions out of the PRD; they live inopen-questions.md.
Boundaries
Owns the testable requirements. review-risks owns surfacing risk and assumptions; design-technical owns HOW. Reached by plan-system.
Return
One line: the artifact written and a terse status, or blocked: <reason>.
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 · 39 lines · 11 tokens per session scan A ef8b9e24f313
define-requirements is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 356 once invoked, about $0.0001 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
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
requirements-author
Requirements authoring guide for BRD and PRD across Discover, Define, and Govern with canonical templates and handoff contracts.
mps-aspect-actions
Use when defining or editing MPS node factories (the "actions" aspect) — NodeFactories roots, per-concept NodeFactory setup functions that initialize a freshly created node and optionally copy data from a replaced sampleNode, plus the actions aspect's CopyPasteHandlers and PasteWrappers roots. Reach for this skill…
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
api-design
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
crypto-market-rank
Crypto market rankings and leaderboards. Query trending tokens, top searched tokens, Binance Alpha tokens, tokenized stocks, social hype sentiment ranks, smart money inflow token rankings, top meme token rankings from Pulse launchpad, and top trader PnL leaderboards. Use this skill when users ask about token rankings…