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 commands/kumaran-is/claude-code-onboarding/aidlcgit clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/commands/kumaran-is/claude-code-onboarding/aidlc)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/aidlc"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/aidlc.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.00000 | $0.05463 |
| Opus 5 | $0.00000 | $0.02731 |
| Sonnet 5 | $0.00000 | $0.01093 |
| Haiku 4.5 | $0.00000 | $0.00546 |
Grade A, and why
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 542 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-DLC Workflow
This workflow is active ONLY when explicitly invoked via
/aidlc. It does NOT override the project's CLAUDE.md rules — both apply concurrently. Project-specific constraints defined in CLAUDE.md remain non-negotiable.
Adaptive Workflow Principle
The workflow adapts to the work, not the other way around.
The AI model intelligently assesses what stages are needed based on:
- User's stated intent and clarity
- Existing codebase state (if any)
- Complexity and scope of change
- Risk and impact assessment
MANDATORY: Rule Details Loading
CRITICAL: When performing any phase, you MUST read and use relevant content from rule detail files. Check these paths in order and use the first one that exists:
.aidlc-rule-details/(Cursor, Cline, Claude Code, GitHub Copilot).kiro/aws-aidlc-rule-details/(Kiro IDE and CLI).amazonq/aws-aidlc-rule-details/(Amazon Q Developer)
All subsequent rule detail file references (e.g., common/process-overview.md, inception/workspace-detection.md) are relative to whichever rule details directory was resolved above.
Common Rules: ALWAYS load common rules at workflow start:
- Load
common/process-overview.mdfor workflow overview - Load
common/session-continuity.mdfor session resumption guidance - Load
common/content-validation.mdfor content validation requirements - Load
common/question-format-guide.mdfor question formatting rules - Reference these throughout the workflow execution
MANDATORY: Extensions Loading (Context-Optimized)
CRITICAL: At workflow start, scan the extensions/ directory recursively but load ONLY lightweight opt-in files — NOT full rule files. Full rule files are loaded on-demand after the user opts in.
Loading process:
- List all subdirectories under
extensions/(e.g.,extensions/security/,extensions/compliance/) - In each subdirectory, load ONLY
*.opt-in.mdfiles — these contain the extension's opt-in prompt. The corresponding rules file is derived by convention: strip the.opt-in.mdsuffix and append.md(e.g.,security-baseline.opt-in.md→security-baseline.md) - Do NOT load full rule files (e.g.,
security-baseline.md) at this stage
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.
- yesterday First seen · 542 lines · 0 tokens per session scan A 22b9d9c22a87
aidlc is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,463 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-03.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
session-log
Create or append a session log entry.
my-tasks
Track, prioritize, and execute tasks with goal alignment and due date awareness. Claude doesn't just remind you — it helps get work done.