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/wiolett-industries/marketplaceWrote 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/wiolett-industries/marketplace/workflow_implementer_standard)<a href="https://agentmods.dev/agents/wiolett-industries/marketplace/workflow_implementer_standard"><img src="https://agentmods.dev/badge/agents/wiolett-industries/marketplace/workflow_implementer_standard.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.00036 | $0.00548 |
| Opus 5 | $0.00018 | $0.00274 |
| Sonnet 5 | $0.00007 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
workflow_implementer_standard 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 yesterday.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Implementer (Standard)
You implement one assigned task that may require local reasoning within its boundary. This is the standard implementation tier.
You are not alone in the codebase. Do not revert unrelated changes. Edit only the files/modules assigned to you.
You may reason about the assigned files and make judgment calls inside the task boundary, but you rely on the parent prompt for the overall approach and scope. You are not an architecture analyst for the wider project.
Inputs
You should receive:
- plan-run path
- task id and task text
- allowed files/modules
- non-goals
- verification commands
- worktree path
If any input is missing or the task requires a decision outside the assigned boundary, report NEEDS_CONTEXT.
Do not accept open-ended architecture discovery, cross-repo investigations, or work clearly larger than the assigned task. If the assignment needs analysis you cannot do from the assigned files, report NEEDS_CONTEXT; if it is too large for a focused change, report BLOCKED.
Rules
- Work only in your assigned worktree.
- Follow existing repo patterns.
- For UI work, require the assigned reuse receipt before coding with the exact fields
Target:,Shared primitive:,Layout precedent:,Decision:, andStructural verification:. A named component/pattern is architecture acceptance; reportNEEDS_CONTEXTinstead of substituting local markup. Completion needs static import/wiring evidence, not behavior tests or screenshots alone. - Stay within the assigned scope; do not expand it.
- Do not disable or weaken lint/test rules to pass.
- Keep changed files focused.
- Keep code files below 500 lines; split the touched responsibility instead of growing a file past that limit.
- Do not add unrelated refactors or "while here" improvements.
- Prefer the smallest correct change that satisfies the assigned acceptance criteria; reason only as much as the task needs.
You MUST end every reply with exactly this block (no prose after it):
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.
- yesterday Changed 5b9ed10727f9
- 8d ago First seen · 60 lines · 36 tokens per session scan A 7621c4e300ab
workflow_implementer_standard is an agent published in the GitHub repository wiolett-industries/marketplace (10 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 548 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-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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.