principal-developer

A lead development agent that turns approved plans into technology-aware implementation plans and coordinates specialist developers. It is used after the project receives approval to proceed.

In plain words
What is it for?
Use it to plan implementation, assign work to development specialists, and review the quality of their completed work.
Why use it?
It gives development work a clear coordinator and a final quality check. The description does not specify which technologies or planning formats it supports.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/vedanta/the-system/principal-developer
Clone the repo
git clone --depth 1 https://github.com/vedanta/the-system

Made for: Claude Code.

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,804 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00033 $0.04804
Opus 5 $0.00016 $0.02402
Sonnet 5 $0.00007 $0.00961
Haiku 4.5 $0.00003 $0.00480

Measured 2d ago against content hash 86e2b441ec62, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

principal-developer 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 2d 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/agents/principal-developer.md · 585 lines

The source is not reproduced here

Licensed LGPL-3.0

The repository is licensed LGPL-3.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. 2d ago First seen · 585 lines · 33 tokens per session scan A 86e2b441ec62

Subscribe to this mod's changes

principal-developer is an agent published in the GitHub repository vedanta/the-system (9 stars, last pushed 6mo ago), licensed LGPL-3.0. It adds 33 tokens to every session and 4,804 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

library_book_renewal.sop

This SOP guides the Library Book Renewal Agent through processing user requests to renew library books while ensuring compliance with library policies, proper workflow execution, and positive user communication.

strands-agents/samples · 0 tokens

huyen-agents

Updated 2025: This is a summary of Chip Huyen's blog and book chapter on agents, with some added context to provide a comprehensive overview of their design, capabilities, and practical applications.

alirezadir/Agentic-AI-Systems · 0 tokens

sanitization-auditor

Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…

Enovatr-Labs/SpecRoute · 125 tokens

roster

Cross-vendor inventory of agents for a SpecRoute-driven project. The roster is grouped by department; each row records the agent's intended model tier, its UI color, its memory scope, and whether it is expected to do web research.

Enovatr-Labs/SpecRoute · 0 tokens

agent-roster-architect

Use when designing or extending the consumer-facing agent roster under agents/. Owns agents/agent-template.md (frontmatter contract), agents/archetypes/ (role concepts - product, architect, backend, frontend, security, qa, devops), agents/examples/ (flat .md files showing real frontmatter shape), and agents/roster.md…

Enovatr-Labs/SpecRoute · 134 tokens

framework-docs-author

Use when drafting or revising framework documentation under agentic-docs/. Owns philosophy.md, spec-driven-development.md, agentic-coding-model.md, automation-decision-framework.md (Skill vs Agent vs Command vs Hook decision matrix), documentation-structure.md, two-tier-docs-pattern.md, multi-vendor-context-files.md…

Enovatr-Labs/SpecRoute · 152 tokens