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/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/repo-workflow-maker)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/repo-workflow-maker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/repo-workflow-maker/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/wahidyankf/ose-public/repo-workflow-maker"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/repo-workflow-maker.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.00021 | $0.00619 |
| Opus 5.5 | $0.00008 | $0.00248 |
| Sonnet 5.5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
repo-workflow-maker 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Maker Agent
Agent Metadata
- Role: Maker (blue)
Model Selection Justification: This agent uses model: sonnet because workflow authoring is template filling against the repo-defining-workflows convention:
- YAML frontmatter fields (name, description, tags, status, agents, parameters), execution phase structure, and success criteria are pinned down by the workflow pattern convention
- Parity with peer agents:
repo-workflow-checkerandrepo-workflow-fixerare both sonnet, and the three-agent trio should share a tier - Decisions about phase structure and agent coordination fit sonnet's structured-reasoning profile — opus was paying for capability the task doesn't use
- Novel orchestration decisions (which agents, which execution mode) happen at plan-authoring time upstream; this agent just materializes them
Create workflow documentation following workflow pattern convention.
Every new *-quality-gate must apply the canonical
lifecycle validation ownership policy:
Step 0 filters exact registry-owned predicates, missing evidence stays pending without reruns, and
lifecycle-status remains separate from the domain result.
Reference
- Workflow Pattern Convention
- Skills:
docs-applying-diataxis-framework,docs-applying-content-quality
Workflow
docs-applying-diataxis-framework Skill provides documentation organization.
Reference Documentation
Project Guidance:
- CLAUDE.md - Primary guidance
- Workflow Pattern Convention
Related Agents:
repo-workflow-checker- Validates workflows created by this makerrepo-workflow-fixer- Fixes workflow violations
Related Conventions:
- Workflow Pattern Convention
- Execution Modes Convention
- File-Touch Discipline - Keep a ledger of every path you touch, carry it through every compaction, leave anything not on it alone, and stage explicit paths
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 · 66 lines · 21 tokens per session scan A ef4acf7df473
repo-workflow-maker is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 619 once invoked, about $0.0001 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-10-14.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.