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/saitarrun/devforge-ai/sdlc-navigategit clone --depth 1 https://github.com/saitarrun/Devforge-aiWhat 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.00023 | $0.00466 |
| Opus 5 | $0.00012 | $0.00233 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
sdlc-navigate 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 3d 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
Codebase Map & Navigation Command
This command enables rapid structural exploration and architectural understanding of large codebases, monorepos, and multi-service repositories.
Usage
/sdlc-navigate "AuthService" # Trace callers, callees, and dependencies
/sdlc-navigate src/billing/ --deep # Map module boundaries and coupling
/sdlc-navigate "processPayment" --impact # Show what breaks if this function is modified
/sdlc-navigate "architecture" # High-level domain topology & service map
Process
- Load Structural Knowledge Graph:
- Query
code-review-graph(or AST analyzer) for symbol relationships, call hierarchies, and coupling metrics.
- Query
- Trace Ingress to Egress:
- Map entrypoint controllers/routes down to service abstractions, database queries, and emitted events.
- Analyze Module Boundaries:
- Identify circular dependencies, layered architecture violations, and shared package imports.
- Synthesize Clean Visual Map:
- Produce a concise summary of symbols, caller chains, data flows, and architectural constraints.
Output Format
### 🗺️ Codebase Map: [Target Symbol / Module]
**Domain Context**: [Service/Package responsible for this logic]
**Location**: `path/to/definition.ts`
#### 🔗 Dependency & Call Chain
- **Ingress Entrypoints**:
- `GET /api/v1/resource` -> `Controller.handleRequest()`
- **Core Orchestrator**:
- `Service.executeBusinessLogic()`
- **Persistence & Egress**:
- `Repository.save()` -> PostgreSQL Table: `resources`
- Event Bus: Emits `ResourceCreatedEvent` -> Kafka Topic: `events.resource`
#### ⚠️ Impact & Coupling Analysis
- **Direct Consumers**: 4 services / 12 callers
- **Risk Level**: Low / Moderate / High (Shared Public API)
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.
- 3d ago First seen · 51 lines · 23 tokens per session scan A 80676a090f86
sdlc-navigate is a command published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 23 tokens to every session and 466 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 commands, from other repositories
sdlc-dev
Phase 3 — Development & Coding. Spawns 9 agents with 4 parallel groups: backend-engineer, frontend+mobile, database, fullstack-engineer.
sdlc-parallel
Run multiple agents in parallel across phases with shared context and collaboration.
sdlc-plan
Phase 1 planning — grill-me interview + 4 sequential agents (product-manager → business-analyst → software-architect → security-architect).
sdlc-ops
Phase 6 — Operations & Monitoring. Spawns sre-engineer, secops-analyst, data-engineer, release-manager (all in parallel).
sdlc-test
Phase 4 — Testing & Security. Spawns qa-manual-tester, automation-qa-engineer, appsec-engineer, penetration-tester, performance-engineer.
sdlc-deploy
Phase 5 — Infrastructure & Deployment. Spawns devops-engineer and cloud-engineer to design CI/CD, containerization, and cloud infrastructure.