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.
npx skills add aws-samples/sample-agent-assisted-sdlc --skill pr-verificationgit 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/skills/aws-samples/sample-agent-assisted-sdlc/pr-verification)<a href="https://agentmods.dev/skills/aws-samples/sample-agent-assisted-sdlc/pr-verification"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-agent-assisted-sdlc/pr-verification/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/skills/aws-samples/sample-agent-assisted-sdlc/pr-verification"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-agent-assisted-sdlc/pr-verification.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.00021 | $0.00332 |
| Opus 5.5 | $0.00008 | $0.00133 |
| Sonnet 5.5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
pr-verification 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
Run this procedure before any action that reports "already merged" or creates a PR.
Uses ONLY state + mergedAt for control flow; mergeStateStatus is diagnostic-only.
- Resolve the branch name
feat/issue-{number}from project.json. - Call
mcp__gateway__source-control___list_pull_requestswithhead={owner}:feat/issue-{number}(REST-filtered fast path). If empty or errors, list open PRs and matchheadRefName == feat/issue-{number}client-side (fallback). - If a PR is found, call
mcp__gateway__source-control___pull_request_readand readstate,mergedAt,mergeStateStatus. LogmergeStateStatusas diagnostic context only — it MUST NOT drive any branching decision. - Four-way decision using ONLY
state+mergedAt:mergedAtnot null → already merged. Set labels["{{LABEL_PREFIX}}:pr-completed"], post comment, exit.state == OPENANDmergedAtnull → open PR exists. Do NOT create a duplicate. Fall through to existing flow.state == CLOSEDANDmergedAtnull → closed without merge. Set labels["{{LABEL_PREFIX}}:error"], post comment, exit.- No PR found → MUST NOT report success. Continue to implement+pr flow.
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 · 17 lines · 21 tokens per session scan A 58aa41aca181
pr-verification is a skill published in the GitHub repository aws-samples/sample-agent-assisted-sdlc (47 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 332 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 skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.