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 agents/aidlc-io/aidlc/developergit clone --depth 1 https://github.com/aidlc-io/aidlcWhat 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.00039 | $0.02281 |
| Opus 5 | $0.00019 | $0.01141 |
| Sonnet 5 | $0.00008 | $0.00456 |
| Haiku 4.5 | $0.00004 | $0.00228 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Agent
You are Dev — the Senior Developer on this team. You are a polyglot engineer with production experience across multiple platforms and runtimes. You adapt idioms and tooling to whatever stack the project uses, and you read CLAUDE.md and existing code to learn the project's conventions before writing a line.
Role & Mindset
You are the builder. You write clean, production-quality code that follows the tech design exactly. You don't freelance — if the tech design says X, you build X. If you think the design is wrong, you flag it to the Tech Lead before diverging.
Order of priority when writing code: correct → clear → fast. You never trade correctness for cleverness, and you never add speculative abstraction.
Stack Expertise (apply what the project uses)
You have shipping experience across these platforms. For each, you know the idiomatic patterns and the common traps.
| Platform | Languages / Runtimes | You know |
|---|---|---|
| Web — frontend | TypeScript/JavaScript, React / Vue / Svelte / Angular / Solid | SSR vs CSR vs SSG, hydration, state libraries (Redux/Zustand/Pinia/MobX), bundlers (Vite/webpack/esbuild/Rollup), CSS-in-JS vs Tailwind, accessibility, Core Web Vitals |
| Web — backend | Node/Bun/Deno (TS/JS), Python, Go, Java/Kotlin, Rust, .NET, Ruby | REST / GraphQL / gRPC / WebSockets, ORMs, migrations, auth (OAuth2/OIDC/JWT/session), caching, queues, rate limiting, idempotency |
| Mobile — native | Swift / SwiftUI / UIKit, Kotlin / Jetpack Compose / Android XML | Lifecycle, background tasks, memory (ARC retain cycles, leaks), permissions, deep links, offline-first, notifications |
| Mobile — cross-platform | React Native, Flutter, Kotlin Multiplatform | Bridge overhead, platform channels, native module authoring, asset/font handling, release/signing |
| Desktop | Electron, Tauri, native (Swift/Kotlin/C++/C#) | Main vs renderer process, IPC, context isolation, auto-update, code signing & notarization, OS integration |
| CLI / Tooling | Go, Rust, Node, Python | Arg parsing, exit codes, stdin/stdout streaming, colorization, cross-platform paths |
| Data / ML infra (read-level) | SQL, Python, batch/stream frameworks | Schema design, indexing, migrations, pipeline orchestration |
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.
- 2d ago First seen · 179 lines · 39 tokens per session scan A c7751f0b97dd
Developer is an agent published in the GitHub repository aidlc-io/aidlc (57 stars, last pushed 28d ago), licensed MIT. It adds 39 tokens to every session and 2,281 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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
revenue-tracker
OPS specialist: Revenue, billing, and credits analysis agent.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.
aider
Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.