sruja-workflow-aidlc

sruja-workflow-aidlc is a command for Claude Code, Cursor from sruja-ai/sruja. It costs 19 tokens per session (609 once invoked), scanned A, original, Apache-2.0.

A command guide for running one phase of an AI-DLC workflow with Sruja. AI-DLC is a staged way to develop software, divided here into inception, construction, and operations.

In plain words
What is it for?
Use it to start or continue a phase, install workflow rules, check project status, record affected areas, create inception documents, request design review, and approve or advance a phase.
Why use it?
It provides checks and approval steps for moving between phases, helping keep planning documents, rules, and implementation work in the right places.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md). Also seen: mentions AGENTS.md.

Good fit Use it to start or continue a phase, install workflow rules, check project status, record affected areas, create inception documents, request design review, and approve or advance a phase.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sruja-ai/sruja/sruja-workflow-aidlc
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/sruja-ai/sruja

Made for: Claude Code, 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 sruja-workflow-aidlc

README.md
[![agentmods](https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-workflow-aidlc/github.svg)](https://agentmods.dev/commands/sruja-ai/sruja/sruja-workflow-aidlc)
Your own site
<a href="https://agentmods.dev/commands/sruja-ai/sruja/sruja-workflow-aidlc"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-workflow-aidlc/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 sruja-workflow-aidlc

Your own site · 80×15
<a href="https://agentmods.dev/commands/sruja-ai/sruja/sruja-workflow-aidlc"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-workflow-aidlc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 609 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00609
Opus 5 $0.00010 $0.00304
Sonnet 5 $0.00004 $0.00122
Haiku 4.5 $0.00002 $0.00061

Measured 10d ago against content hash 963eb56a8f3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

sruja-workflow-aidlc 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 10d 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.

.cursor/commands/sruja-workflow-aidlc.md · 59 lines

How it starts

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

You are driving one phase of an AI-DLC workflow integrated with Sruja. Obey AGENTS.md and docs/AIDLC_INTEGRATION.md.

The user must provide a phase: inception, construction, or operations.

Shared setup (all phases)

  1. Confirm repo root (-r .).
  2. If no workflow exists, run:
    sruja workflow init -r . --title "<short title>" --with-aidlc --install-aidlc-rules
    
  3. Otherwise ensure rules are installed:
    sruja workflow install-rules -r .
    
  4. Load AIDLC steering from .aidlc/aidlc-rules/ and rule details from .aidlc-rule-details/ (follow core-workflow.md).
  5. Before large edits, run:
    sruja workflow status -r . --check
    
    If it fails, fix listed missing / aidlc_missing items before proceeding.

Phase — inception

  • Ensure inception/scope.md and run sruja workflow record-impact -r . --id <id> when target_elements are set.
  • Produce AIDLC artifacts under inception/aidlc-docs/ (never mix app code into aidlc-docs).
  • Optional grounded review:
    sruja workflow design-review -r . --id <id>
    
  • When ready: sruja workflow approve -r . --id <id> --phase inception then sruja workflow advance.

Phase — construction

  • Gate must pass (workflow status --check); inception must be approved in strict mode.
  • Use .cursor/commands/sruja-plan-feature.md for task-layer construction/task-plan.md.
  • Link proposals in construction/linked_proposal_ids.json; use sruja propose create --workflow-id <id>.
  • App code in repo root or workspace/; run project tests / just check (or make check) as appropriate.
  • Approve construction phase when artifacts and proposals are ready.

Phase — operations

  • Ensure operations/deploy-scope.json exists.
  • Run sruja drift -r . -a repo.sruja and resolve violations before operations approval.
  • Approve operations when deploy scope and drift are clean.

Audit

After significant stage steps:

sruja workflow audit -r . --id <id> --event "stage complete: <name>"

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

  1. 10d ago First seen · 59 lines · 19 tokens per session scan A 963eb56a8f3b

Subscribe to this mod's changes

sruja-workflow-aidlc is a command published in the GitHub repository sruja-ai/sruja (24 stars, last pushed 3d ago), licensed Apache-2.0. It adds 19 tokens to every session and 609 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-30.