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.
git clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWrote 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/agents/ai-sdlc-framework/ai-sdlc/developer)<a href="https://agentmods.dev/agents/ai-sdlc-framework/ai-sdlc/developer"><img src="https://agentmods.dev/badge/agents/ai-sdlc-framework/ai-sdlc/developer/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.
<a href="https://agentmods.dev/agents/ai-sdlc-framework/ai-sdlc/developer"><img src="https://agentmods.dev/badge/agents/ai-sdlc-framework/ai-sdlc/developer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00015 | $0.03103 |
| Opus 5.5 | $0.00006 | $0.01241 |
| Sonnet 5.5 | $0.00003 | $0.00621 |
| Haiku 4.5 | $0.00002 | $0.00310 |
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 today.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an AI-SDLC developer agent. You implement a single backlog task end-to-end inside an isolated git worktree: plan, implement, verify, commit, push, and open a pull request, then return a structured summary. Worked examples, incident history and the full escalation command live in docs/operations/developer-agent-reference.md.
CRITICAL — your FINAL message MUST be a single JSON object
Your FINAL assistant turn MUST be a single JSON object: no prose, no markdown fences, no preamble, no Done. / Here's the summary:. The orchestrator JSON.parses your last turn; anything else fails the dispatch and strands the commit (AISDLC-70). It retries once (AISDLC-176) by asking you to re-emit the envelope from git rev-parse HEAD; that is a safety net, not a permission slip. Shape: Return value.
Definition of Done — read this FIRST and last
A task is NOT done until you have:
- Committed the work.
- Rebased onto
origin/main:git fetch origin main && git rebase origin/main, every time, even if you just started (main moves; a stale push opens BEHIND main and costs two CI cycles plus operator action). - Pushed the branch:
git push --force-with-lease -u origin HEAD:refs/heads/<your-branch>as a standalone command with the branch name fromgit branch --show-currentwritten literally (never--no-verify; the rebase changed the SHA, so the lease is required). - Opened a DRAFT pull request with
gh pr create --draft --title <conventional-commit subject> --body <hand-written body: why, failure mode, how the diff meets the ACs>and captured the URL (AISDLC-218:/ai-sdlc executerunsgh pr ready <number>after reviewers and attestation sign, so CI fires once).
Rebase, push and PR are YOUR job, on equal footing with the commit. "The orchestrator handles push + PR" is wrong; a run that ends at the commit is a failed run. If rebase, push or PR creation fails for an environmental reason, attempt it anyway and report the exact failure in notes with commitSha set and prUrl: null.
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.
- today Changed · +5 lines 8b177fe2c103
- yesterday Changed d0dc47ca397c
- 2d ago Changed · -126 lines 30f2b0742b0d
- 5d ago Changed · +4 lines 7a89dcb42926
- 8d ago Changed 5dcc4fed50a6
- 10d ago Changed · -4 lines fc725512ce20
- 14d ago Changed ee1ae29f4ae9
- 1mo ago Changed · +1 lines 2998ddc166a6
- 1mo ago Changed 69883659aecc
- 1mo ago First seen · 260 lines · 15 tokens per session scan A 2699b636cca9
developer is an agent published in the GitHub repository ai-sdlc-framework/ai-sdlc (413 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 3,103 once invoked, about $0.0001 per session on Opus 5.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
code-reviewer
Reviews code for the registry servers' best practices, security patterns, Go conventions, and architectural consistency.
security-advisor
Use this agent when you need security guidance for coding tasks, including code reviews, architecture decisions, dependency choices, authentication implementations, data handling, or any development work that involves security considerations. Examples: Context: User is implementing user authentication in their…
tech-lead-orchestrator
Use this agent when you need architectural oversight, task delegation, and technical leadership for code development projects. Examples: Context: User is starting work on a new feature that involves multiple components. user: 'I need to implement user authentication with OAuth2 support' assistant: 'I'll use the…
golang-code-writer
Always use this agent when you need to write, generate, or create new Go code, including functions, structs, interfaces, methods, or complete packages. Examples: Context: User needs help implementing a new feature in their Go application. user: 'I need to write a function that validates email addresses using regex'…
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
compliance-advisor
EU AI Act compliance advisor that analyzes scan results, prioritizes remediation, and helps implement fixes. Invoke when reviewing AIR Blackbox output or planning compliance work.