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 skills add Jacobinwwey/notemdpro --skill workflow-runnergit clone --depth 1 https://github.com/Jacobinwwey/notemdproWrote 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/skills/jacobinwwey/notemdpro/workflow-runner)<a href="https://agentmods.dev/skills/jacobinwwey/notemdpro/workflow-runner"><img src="https://agentmods.dev/badge/skills/jacobinwwey/notemdpro/workflow-runner/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/skills/jacobinwwey/notemdpro/workflow-runner"><img src="https://agentmods.dev/badge/skills/jacobinwwey/notemdpro/workflow-runner.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.00016 | $0.00510 |
| Opus 5.5 | $0.00006 | $0.00204 |
| Sonnet 5.5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
workflow-runner 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 16d 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.
What it actually says
Workflow runner
English
Create one task identity and ordered stage list for the user's request. Track each stage's inputs, outputs and status (pending, running, completed, failed, cancelled, unavailable). A stage consumes only verified output from its dependencies. Preserve earlier outcomes when another stage starts or fails.
Retain full diagnostic records with stage, severity (error|warning|info), kind, message, source path and suggested action. Group by severity plus kind, never tag alone. In CLI summaries show counts and errors by default; keep warnings/information available in the full report. If the host offers disclosures, close the entire panel without errors, otherwise open only error groups. This skill does not provide a UI component.
Write an authorized task report with all stage outcomes and artifact paths, or return it in the conversation when file output was not requested. Never erase previous stage logs on a progress reset. Clear a retained report only on explicit user instruction. Redact credentials and provider payloads. Distinguish a successful source generation from preview/export success and preserve partial outputs on failure.
中文
为用户请求建立一个任务标识与有序阶段列表,记录每阶段的输入、输出及状态(pending、running、completed、failed、cancelled、unavailable)。阶段只消费已验证的依赖输出,后续阶段开始或失败时仍保留前序结果。
完整诊断记录包含 stage、severity(error|warning|info)、kind、消息、来源路径和建议操作。按严重级别加标签分组,不能仅按标签合并。CLI 摘要默认显示计数与错误,完整报告保留警告及信息。若宿主提供折叠界面,无错误时整体收起,有错误时仅展开错误组。本技能不提供界面组件。
在已授权范围内写入包含所有阶段结果和产物路径的报告;未请求文件输出时在会话中返回。进度重置不得擦除前序日志,只在用户明确要求时清空保留的报告。隐去凭据及 provider 载荷,区分源生成与预览/导出成功,失败时保留部分产物。
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.
- 16d ago First seen · 23 lines · 16 tokens per session scan A c8588d340ea1
workflow-runner is a skill published in the GitHub repository Jacobinwwey/notemdpro (2 stars, last pushed 16d ago), licensed MIT. It adds 16 tokens to every session and 510 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-05.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…