A requirements-management command for AUTOSAR projects. It stores requirements with stable IDs and links them to the code, tests, and documentation that support them.

Use it to add requirements, change their status with a reason, and check whether requirement references are present across the project.

It helps prevent requirements from becoming disconnected from the implementation or tests, and identifies missing or unused links.

How melodypapa/py-armodel configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to melodypapa/py-armodel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/melodypapa/py-armodel/main/.claude/commands/req.md

Clone the repo

git clone --depth 1 https://github.com/melodypapa/py-armodel

Made for: Claude Code.

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/commands/melodypapa/py-armodel/req/github.svg)](https://agentmods.dev/commands/melodypapa/py-armodel/req)

Your own site

<a href="https://agentmods.dev/commands/melodypapa/py-armodel/req"><img src="https://agentmods.dev/badge/commands/melodypapa/py-armodel/req/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/melodypapa/py-armodel/req"><img src="https://agentmods.dev/badge/commands/melodypapa/py-armodel/req.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 593 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 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.1	$0.00000	$0.00593
Opus 5.5	$0.00000	$0.00237
Sonnet 5.5	$0.00000	$0.00119
Haiku 4.5	$0.00000	$0.00059

Measured 5d ago against content hash 984de494be91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

req 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 5d 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.

.claude/commands/req.md · 76 lines

How it starts

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

Requirement Management

Manage AUTOSAR project requirements with traceability to code, tests, and documentation.

Actions

When the user runs /req, help manage requirements based on $ARGUMENTS:

Add New Requirement

Add requirement to docs/requirements/requirements.md
Assign stable ID: SWR_<MODULE>_<NUMBER> (next available number)
Include required sections:
- Title
- Maturity (draft/accept/invalid)
- Description
Link to related code and tests

Update Requirement Maturity

Change maturity level (draft → accept → invalid)
Document why the change was made
Never change the requirement ID

Traceability Check

Search code for requirement ID references in docstrings
Verify tests reference requirements they validate
Check CLAUDE.md for requirement listings
Report any orphaned requirements or missing traceability

Requirement Formats

Requirements: SWR_<MODULE>_<NUMBER>

Example: SWR_MODEL_00001, SWR_PARSER_00003

Tests: SWUT_<MODULE>_<NUMBER>

Example: SWUT_MODEL_00001, SWUT_PARSER_00002

Coding Rules: CODING_RULE_<CATEGORY>_<NUMBER>

Example: CODING_RULE_IMPORT_00001, CODING_RULE_STYLE_00003

Maturity Levels:

draft: Newly created, under review, or not yet implemented
accept: Accepted, implemented, and validated
invalid: Deprecated, superseded, or no longer applicable

Critical Rules

STABLE IDs ARE PERMANENT

Once assigned, requirement IDs must NEVER be changed
Even if the requirement is removed or superseded
Use the next available number for new requirements
Never reuse a deleted ID

Usage Examples

/req add SWR_WRITER_00007 "Add support for custom markdown templates"
/req update SWR_WRITER_00006 maturity accept
/req check traceability
/req list draft
/req search parser

Requirements by Module

Model: SWR_MODEL_00001 - SWR_MODEL_00013
Parser: SWR_PARSER_00001 - SWR_PARSER_00007
Writer: SWR_WRITER_00001 - SWR_WRITER_00006
CLI: SWR_CLI_00001 - SWR_CLI_00011
Package: SWR_PACKAGE_00001 - SWR_PACKAGE_00003

Read the full file on GitHub · 76 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.

5d ago First seen · 76 lines · 0 tokens per session scan A 984de494be91

Subscribe to this mod's changes

req is a command published in the GitHub repository melodypapa/py-armodel (18 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 593 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-11-01.

Project management arxml autosar parser writer

req next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
reqmelodypapa/py-armodel	Command	18	14d ago	MIT	A	0	Claude Code
arxml-validatejasontaotao/claude-autosar	Command	2	4mo ago	none	A	64	Claude Code
bsw-configjasontaotao/claude-autosar	Command	2	4mo ago	none	A	72	Claude Code
eb-savejasontaotao/claude-autosar	Command	2	4mo ago	none	A	63	Claude Code
exportjasontaotao/claude-autosar	Command	2	4mo ago	none	A	55	Claude Code
logjasontaotao/claude-autosar	Command	2	4mo ago	none	A	52	Claude Code
session-treejasontaotao/claude-autosar	Command	2	4mo ago	none	A	48	Claude Code

py-armodel: Command for Claude Code