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 commands/aws/agent-toolkit-for-aws/release-testinggit clone --depth 1 https://github.com/aws/agent-toolkit-for-awsWhat 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.00020 | $0.00813 |
| Opus 5 | $0.00010 | $0.00407 |
| Sonnet 5 | $0.00004 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
release-testing 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read and follow the running-release-tests skill for full execution details.
Step 0 — Choose your execution path (DO THIS FIRST)
Check your available tools. Do you have ALL of these tools?
aws_devops_agent__create_release_testing_jobaws_devops_agent__get_taskaws_devops_agent__list_journal_recordsaws_devops_agent__get_release_ui_testing_reportaws_devops_agent__get_release_api_testing_report
These tools are NOT deferred/lazy-loaded — if they do not appear in your tool list, they are unavailable. Do NOT search for them via ToolSearch.
- YES (all present) → Use the "Remote Server" path (steps 4-8 below)
- NO → Tell the user: "Remote server not configured." Then prompt the user with instructions from the
setup-devops-agentskill if they intend to set up the connection. If not, mention that you are "proceeding with the AWS CLI fallback." Then use the Fallback (CLI) path below.
Steps 1-3 — Common to both paths (see skill: "Gathering test parameters")
- If
$ARGUMENTScontains a test profile ID (e.g.,ki-12345), use it directly. - If
$ARGUMENTSis empty, ask the user which test profile to use. - Ask if the user has a specific test requirement or focus area.
Steps 4-8 — Remote Server path (see skill: "Core workflow")
- Call
aws_devops_agent__create_release_testing_job(test_profile_id="...", webhook_event_message="..."). - Tell the user tests take 10+ minutes and you'll keep them posted.
- Poll
aws_devops_agent__get_task(task_id=TASK_ID)every 30s. - Stream progress via
aws_devops_agent__list_journal_records(execution_id=EXEC_ID, order="ASC"). - On
COMPLETED: callaws_devops_agent__get_release_ui_testing_report(execution_id=EXEC_ID)(UI) oraws_devops_agent__get_release_api_testing_report(execution_id=EXEC_ID)(API), and save to file.
Steps 9-12 — Fallback (CLI) path
Use this path when the remote server tools are unavailable.
- List agent spaces with
aws devops-agent list-agent-spaces --region us-east-1and ask the user which one to use. - Start the job:
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 · 81 lines · 20 tokens per session scan A fd07f77ce983
release-testing is a command published in the GitHub repository aws/agent-toolkit-for-aws (2,498 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 813 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.