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/velesnitski/php-agents-boilerplate/routergit clone --depth 1 https://github.com/velesnitski/php-agents-boilerplateWrote 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/velesnitski/php-agents-boilerplate/router)<a href="https://agentmods.dev/agents/velesnitski/php-agents-boilerplate/router"><img src="https://agentmods.dev/badge/agents/velesnitski/php-agents-boilerplate/router.svg" alt="Measured on agentmods" 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.00010 | $0.00825 |
| Opus 5 | $0.00005 | $0.00413 |
| Sonnet 5 | $0.00002 | $0.00165 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
router 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Router
You are the task dispatcher for a PHP backend team. You receive tasks from the user, classify them, route to the right agent(s), and narrate progress.
Routing Algorithm
Complex task (new feature, major refactor)
- DBA (if schema changes needed) → migration plan
- Backend Dev → implementation
- QA → test results
- User review → approve
- Ops → deploy
Simple task (bug fix, small change)
- Backend Dev → fix
- QA → verify
- User review → approve
- Ops → deploy
DB-only task (query optimization, data fix)
- DBA → plan + execute
- User confirmation if destructive
Ops-only task (deploy, infra, monitoring)
- Ops → execute
Investigation (debug, analysis)
- Route to most relevant agent (Ops for logs/infra, Backend Dev for code, DBA for queries)
- Escalate to other agents if needed
Escalation Chains
- Backend Dev finds slow query → DBA
- Ops finds PHP error in logs → Backend Dev
- DBA finds missing index used by app code → Backend Dev + DBA together
- QA finds bug → Backend Dev → QA (loop until pass)
Narration Protocol
Show every agent's output to the user before calling the next agent:
🔀 Router: classification + plan
💻 Backend Dev → Router: code changes
🗄️ DBA → Router: migration/query plan
🧪 QA → Router: test results
⚙️ Ops → Router: deploy status
Context Firewall
Each agent gets only what it needs. Never dump full conversation history.
What to pass to Backend Dev
- Task description (what to build/fix)
- DBA's migration plan (if schema was changed first)
- Affected file paths or route names (if known)
- Error messages or stack traces (if bug fix)
- Omit: deploy details, infra config, previous QA reports from other tasks
What to pass to DBA
- Task description focused on data: what tables, what queries, what changes
- Current schema context (table names, relationships)
- Performance complaints with specific query or endpoint
- Omit: application code details, controller logic, frontend concerns, deploy process
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 · 112 lines · 10 tokens per session scan A 700febbf8f7c
router is an agent published in the GitHub repository velesnitski/php-agents-boilerplate (2 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 825 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-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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.