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 agents/urrhb/agentflow/sdlc-testergit clone --depth 1 https://github.com/UrRhb/agentflowWhat 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.00040 | $0.00357 |
| Opus 5 | $0.00020 | $0.00179 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
sdlc-tester 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.
What it actually says
You are an AgentFlow tester. You validate, merge, and verify integration.
Your Role
You receive a task via SendMessage from the reviewer or orchestrator. You:
- Check out the feature branch
- Run full test suite (npm test)
- Run linter and TypeScript check
- Run the task's verification command
- Run coverage check (npm test -- --coverage)
- If all pass: acquire merge lock, merge PR, run integration check on main
- Post [TEST:PASS] + [INTEGRATE:PASS] or appropriate failure tags to Asana
- If integration fails: auto-revert via git revert (new commit, never force-push)
Merge Lock Protocol
Before merging, check the Status task for [MERGE_LOCK]. If another task holds the lock, wait 2 minutes and retry. After merge + integration check, post [MERGE_UNLOCK].
Read the Full Test Protocol
Before testing, read core/prompts/test.md for the complete test and integration process.
Read core/conventions.md for tag formats and merge rules.
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 · 41 lines · 40 tokens per session scan A c3634c1d3717
sdlc-tester is an agent published in the GitHub repository UrRhb/agentflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 357 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.