Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflownpx agentmods add commands/bybren-llc/safe-agentic-workflow/test-pr-dockerWrote 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/commands/bybren-llc/safe-agentic-workflow/test-pr-docker)<a href="https://agentmods.dev/commands/bybren-llc/safe-agentic-workflow/test-pr-docker"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/test-pr-docker/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/commands/bybren-llc/safe-agentic-workflow/test-pr-docker"><img src="https://agentmods.dev/badge/commands/bybren-llc/safe-agentic-workflow/test-pr-docker.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.00007 | $0.00708 |
| Opus 5.5 | $0.00003 | $0.00283 |
| Sonnet 5.5 | $0.00001 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
test-pr-docker scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:3000/api/health Copies of this mod
2 near-identical copies found in the catalogue:
- test-pr-docker — 97% identical, 12 lines differ
- test-pr-docker — 92% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.
Test the Docker registry PR workflow by adding the build-docker-image label to a PR and verifying the build.
Workflow
1. Get PR Number
If argument provided ($1):
- Use as PR number
- Fetch PR details:
gh pr view $1
If no argument:
- Check if current branch has open PR
- Extract PR number from branch
2. Add Label to PR
Add build-docker-image label:
gh pr edit {PR-number} --add-label "build-docker-image"
Confirm label added:
gh pr view {PR-number} --json labels
3. Monitor Build
Explain to user:
- GitHub Actions will build Docker image (~5-10 min)
- Image will be tagged as
pr-{number} - Build status visible in PR checks
- Can monitor at:
https://{{GITHUB_ORG}}/{{PROJECT_NAME}}/actions
Provide link to PR:
gh pr view {PR-number} --web
4. Verification Steps
Once build completes, guide user through verification:
On Linux machine:
# Pull PR-specific image
./scripts/dev-docker.sh pull-pr {PR-number}
# Verify image exists
docker images | grep {{PROJECT_NAME}}
# {{TICKET_PREFIX}}-400: Use {{PROJECT}}_IMAGE_TAG environment variable instead of editing compose file
# Set the tag before running docker compose:
export {{PROJECT}}_IMAGE_TAG=pr-{PR-number}
# Or update docker-compose.staging.yml image tag temporarily:
# Change: image: {{REGISTRY}}/{{PROJECT_NAME}}/dev:${{PROJECT}_IMAGE_TAG:-latest}
# To: image: {{REGISTRY}}/{{PROJECT_NAME}}/dev:pr-{PR-number}
# Restart with PR image
./scripts/dev-docker.sh restart
# Verify services running
./scripts/dev-docker.sh status
# Check health
curl http://localhost:3000/api/health
5. Testing Complete
After verification:
# Revert docker-compose.dev.yml
# Remove label to stop builds
gh pr edit {PR-number} --remove-label "build-docker-image"
Success Criteria
- ✅ Label added successfully
- ✅ GitHub Actions build triggered
- ✅ Image built with pr-{number} tag
- ✅ Image pullable on Linux machine
- ✅ Services start correctly
- ✅ Hot-reload verified
- ✅ Health check passes
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.
- 1mo ago First seen · 124 lines · 7 tokens per session scan A 8fa124821874
test-pr-docker is a command published in the GitHub repository bybren-llc/safe-agentic-workflow (424 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 708 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
review-before-deploy
Execute comprehensive pre-deployment review using code-review-agent with all relevant platform agents. Run complete deployment readiness checklist: verify all tests pass (unit, integration, E2E), security audit clean (no Critical/High issues), performance benchmarks met (Lighthouse > 90), TypeScript compilation…
implement-tasks
A task implementation command that carries out the tasks in a project plan. For code, it can use TDD, a process of writing a failing test before the code that makes it pass; documents and configuration are implemented directly.
ship
Before merging or deploying, run ALL of the following checks. Every gate must pass.
dare-dockerfile
Este comando analisa a stack do projeto (definida no DESIGN.md ou .cursorrules) e gera um Dockerfile otimizado para produção e desenvolvimento.
fix-ci
CI tests are failing for this PR. Use cpp-pro to diagnose and resolve this issue, then push your fixes to the PR and monitor the CI test results using gh until you observe that everything passes correctly. If any further problems should be observed, repeat this diagnose, resolve, push and monitor process until…
sparc-devops
🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...