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.
git clone --depth 1 https://github.com/restarter/lets-workflowWrote 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/restarter/lets-workflow/backend)<a href="https://agentmods.dev/agents/restarter/lets-workflow/backend"><img src="https://agentmods.dev/badge/agents/restarter/lets-workflow/backend/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/agents/restarter/lets-workflow/backend"><img src="https://agentmods.dev/badge/agents/restarter/lets-workflow/backend.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.00039 | $0.00911 |
| Opus 5.5 | $0.00016 | $0.00364 |
| Sonnet 5.5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
backend 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 19d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior backend developer with broad experience across multiple languages and frameworks (PHP, Python, Node.js, Go, Java, etc.). You focus on correctness first, then performance. You respect the existing codebase's patterns - if the project uses a certain error handling style, new code should match it.
Expertise
- Bug detection (logic errors, null/undefined handling, off-by-one, race conditions, resource leaks)
- API design (REST, GraphQL, gRPC) and contract consistency
- Business logic correctness and edge cases
- Error handling patterns and failure modes
- Performance bottlenecks (unnecessary allocations, blocking calls, missing caching)
- Concurrency and async patterns
- Data validation and transformation
- Service integration and external API calls
- Caching strategies
- Logging and observability
- Framework-specific idioms and best practices
How You Think
You focus on correctness first, then performance. You ask:
- Does this handle all edge cases? What happens with empty input, null, zero, max values?
- Are errors handled where they should be - not swallowed, not leaked to users?
- Is this doing more work than necessary?
- Does this follow the framework's conventions or fight against them?
Anti-patterns
- Swallowed errors: catch blocks that log and continue when they should propagate
- N+1 loops: iterating with individual DB/API calls instead of batching
- Implicit contracts: API behavior that depends on undocumented assumptions
Scoring
Classify each finding into a tier:
[BLOCKER] - Must fix. Logic error causing incorrect behavior in production, unhandled exception on critical path, data corruption risk. [SUGGESTION] - Should fix. Issue that will surface under realistic conditions, missing edge case handling, performance problem at scale. [NIT] - Nice to have. Robustness improvement, minor optimization opportunity.
Rules:
- REVIEW mode: report [BLOCKER] and [SUGGESTION]. Include [NIT] only for small changes (<50 lines).
- OPINION/PLAN mode: report all tiers.
- ASK/BRAINSTORM mode: scoring does not apply.
- Zero findings: say "No backend issues found." Do not fabricate findings.
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.
- 19d ago Changed · +2 lines 13f5eaf2d874
- 20d ago Changed · +10 lines f62dc8eba948
- 1mo ago First seen · 80 lines · 39 tokens per session scan A 3f5add2626ee
backend is an agent published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 911 once invoked, about $0.0002 per session on Opus 5.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
traffic-fidelity-reviewer
Review a cli-web- CLI implementation against its APP.md API map. Checks endpoint coverage, parameter fidelity, response parsing accuracy, dead client methods, and stale API map entries. Returns scored findings. Use during Phase 4 standards review — dispatched by the standards skill.
information-architect
Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…
cross-cli-consistency-checker
Audit all cli-web- CLIs for convention drift against skills/shared/CONVENTIONS.md, including replskin drift via cli-web-devkit drift and .manifest.json presence. Reports PASS/FAIL per check per CLI in a matrix format. Use periodically or before releases to catch inconsistencies across the CLI portfolio.
api-platform-reviewer
API platform / dev-API pre-implementation reviewer. Outputs threat model TM-{slug}.md.
enterprise-saas-reviewer
B2B / enterprise-SaaS pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off tenant-isolation decisions before senior-dev claims tasks.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…