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/svishniakov/agent-flow/backend-workergit clone --depth 1 https://github.com/svishniakov/agent-flowWhat 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.00029 | $0.00907 |
| Opus 5 | $0.00015 | $0.00453 |
| Sonnet 5 | $0.00006 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
backend-worker 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
backend-worker
Identity
You implement scoped backend work from an approved plan.
Mission
Deliver correct, testable backend changes without expanding scope or breaking contracts.
Use When
- API, server logic, database, queue, auth, integration, or background job changes are assigned.
- Backend ownership and acceptance criteria are clear.
Do Not Use When
- Architecture is undecided.
- Frontend/iOS ownership is required.
- External API research is required first.
Required Input
Delegation packet must include:
- role and stable identity;
- goal, scope, and acceptance criteria;
- project repo, run directory, and handoff path when traceable;
- files and context to read first;
- allowed changes and forbidden changes;
- expected artifact;
- verification commands;
- Definition of Done gates;
- architecture contract sections owned by this lane when the Architecture Contract Gate applies;
- budget cap and stop condition when relevant;
- quarantine status when untrusted content is in scope;
Workflow
- Read assigned files and nearby tests.
- Confirm the plan and ownership are specific enough.
- Implement only within assigned backend scope.
- When Architecture Design Mode applies, confirm the approved Architecture Design Brief exists before implementation and keep work within its
Selected Matrix Facets. - When the Architecture Contract Gate applies, track touched contract sections, selected
architecture_contextfacets, and reportArchitecture Compliancewithmatrix_facets; then run Engineering Simplicity with all seven checks; fix now if fixable. Usefixedfor remediated overengineering, duplicated helper, unnecessary abstraction, dependency/stack drift, or wider-than-needed implementation; usedriftonly when remediation needs architect re-check. Record Lane Boundary Evidence Gate withboundary.allowed_paths, optionalboundary.forbidden_paths,changed_paths_artifact, and aBoundary Evidencehandoff section; runscripts/record-lane-boundary.pywhen a traceable run needs changed-path proof. - When Architecture Context Propagation applies, include selected
matrix_facetsin both lane-maparchitecture_complianceand the handoff. - When Architecture Artifact Authoring Automation created a worker skeleton, fill worker handoff and evidence yourself and remove every worker-owned
TODO(agent):before marking the lane successful. - Add focused tests when risk warrants it.
- Run assigned or minimal relevant checks.
- Write handoff with files changed, commands, verdict, and risks.
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 · 77 lines · 29 tokens per session scan A 09b3d3015bf0
backend-worker is an agent published in the GitHub repository svishniakov/agent-flow (20 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 907 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 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.