requirements-traceability

requirements-traceability is a cursor rule for Cursor from aws-samples/sample-ramp-aidlc-mod-starter-packs. It costs 0 tokens per session (936 once invoked), scanned A, original, MIT-0.

A rule that applies when work is based on functional documents or screenshots. It requires requirements-traceability practices for document-based and hybrid projects, but not for purely new projects.

In plain words
What is it for?
Use it to decide when to create and review a requirements traceability record during specification-driven development or an application rewrite.
Why use it?
It prevents source requirements from being overlooked or applied where they do not belong.

Cursor rule for Cursor ✓ vendor

Written for Cursor: installed under .cursor/.

Good fit Use it to decide when to create and review a requirements traceability record during specification-driven development or an application rewrite.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/aws-samples/sample-ramp-aidlc-mod-starter-packs/requirements-traceability
About the project

AI-DLC for Modernization Starter Packs is a collection of reusable project templates for applying an AI-driven development lifecycle to application modernization work. Each pack gives teams structured instructions, skills, and agent-tool configurations for use with several coding agents. The catalogue entries are components and tool registrations included in these packs.

aws-samples/sample-ramp-aidlc-mod-starter-packs · 10 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/aws-samples/sample-ramp-aidlc-mod-starter-packs

Made for: Cursor.

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.

agentmods badge for requirements-traceability

README.md
[![agentmods](https://agentmods.dev/badge/rules/aws-samples/sample-ramp-aidlc-mod-starter-packs/requirements-traceability/github.svg)](https://agentmods.dev/rules/aws-samples/sample-ramp-aidlc-mod-starter-packs/requirements-traceability)
Your own site
<a href="https://agentmods.dev/rules/aws-samples/sample-ramp-aidlc-mod-starter-packs/requirements-traceability"><img src="https://agentmods.dev/badge/rules/aws-samples/sample-ramp-aidlc-mod-starter-packs/requirements-traceability/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.

agentmods 80×15 button for requirements-traceability

Your own site · 80×15
<a href="https://agentmods.dev/rules/aws-samples/sample-ramp-aidlc-mod-starter-packs/requirements-traceability"><img src="https://agentmods.dev/badge/rules/aws-samples/sample-ramp-aidlc-mod-starter-packs/requirements-traceability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 936 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00936
Opus 5.5 $0.00000 $0.00374
Sonnet 5.5 $0.00000 $0.00187
Haiku 4.5 $0.00000 $0.00094

Measured 1mo ago against content hash 2a5359da0075, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

requirements-traceability 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.

packs/cots-rewrite-on-cloudnative/scaffolded-packs/cursor/.cursor/rules/requirements-traceability.mdc · 76 lines

The source is not reproduced here

Licensed MIT-0

The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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.

  1. 1mo ago First seen · 76 lines · 0 tokens per session scan A 2a5359da0075

Subscribe to this mod's changes

requirements-traceability is a cursor rule published in the GitHub repository aws-samples/sample-ramp-aidlc-mod-starter-packs (10 stars, last pushed 1mo ago), licensed MIT-0. It costs nothing until one of its globs matches a file; then it loads 936 tokens. 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-23.