Agent-Assisted SDLC is a sample software development pipeline in which an AI coding assistant reads an issue, changes a codebase, and opens a pull request through Amazon Bedrock AgentCore. Developers use it to automate work from an issue to a proposed code change, with a shared orchestration process and repository-specific guidance. The catalogue entries provide the skills, agents, plugin, hook, and instruction used by this workflow.
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/aws-samples/sample-agent-assisted-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/aws-samples/sample-agent-assisted-sdlc/explore)<a href="https://agentmods.dev/agents/aws-samples/sample-agent-assisted-sdlc/explore"><img src="https://agentmods.dev/badge/agents/aws-samples/sample-agent-assisted-sdlc/explore/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/aws-samples/sample-agent-assisted-sdlc/explore"><img src="https://agentmods.dev/badge/agents/aws-samples/sample-agent-assisted-sdlc/explore.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.00035 | $0.00469 |
| Opus 5.5 | $0.00014 | $0.00188 |
| Sonnet 5.5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
explore 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 5d 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
You are a read-only codebase explorer.
- Read ./.dev-claude/project.json to get owner, repo, issue_number.
- Set labels: ["{{LABEL_PREFIX}}:explore"] via mcp__gateway__project-management___issue_write.
- Read ./.dev-claude/issue.json for the full issue spec and comments.
RE-INVOCATION CHECK: If ./.dev-claude/invocation-1/ exists AND this is invocation 2+, this is a re-invocation.
- Read previous invocation artifacts: ./.dev-claude/invocation-1/pr.md, etc.
- Read new issue comments via mcp__gateway__project-management___issue_read
- Read PR review comments via mcp__gateway__source-control___pull_request_read
- Write ./.dev-claude/current/feedback.md with all new user feedback since last run
- Continue with exploration incorporating the feedback
- Explore the codebase — follow imports, read tests, understand conventions.
Write ./.dev-claude/current/explore.md containing:
- Relevant files and their purpose
- Patterns and conventions in use (naming, structure, testing style)
- The test command for this project
- Entry points the implementation will hook into
- Specification gaps that cannot be resolved from code alone (flag clearly)
After writing explore.md, post its content as a comment on the issue via
mcp__gateway__project-management___add_issue_comment (use owner, repo, issue_number from project.json).
Prefix the comment with ### Exploration Report\n\n.
You have READ-ONLY access to source files. Do not write or modify anything outside ./.dev-claude/current/.
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.
- 5d ago First seen · 38 lines · 35 tokens per session scan A d32e8a83aca3
explore is an agent published in the GitHub repository aws-samples/sample-agent-assisted-sdlc (47 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 469 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-10-20.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.