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 CarbeneAI/Forge --skill workfloworchestrationgit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/carbeneai/forge/workfloworchestration)<a href="https://agentmods.dev/skills/carbeneai/forge/workfloworchestration"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/workfloworchestration/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/carbeneai/forge/workfloworchestration"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/workfloworchestration.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.00073 | $0.05784 |
| Opus 5 | $0.00036 | $0.02892 |
| Sonnet 5 | $0.00015 | $0.01157 |
| Haiku 4.5 | $0.00007 | $0.00578 |
Grade B, and why
workflow-orchestration scanned grade B with 2 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 7d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl http://localhost:3000/api/auth/login -d '{"email":"[email protected]","password":"test123"}' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:3000/api/auth/login -d '{"email":"[email protected]","password":"test123"}' How it starts
The opening of the file, as written. The whole thing — 838 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WorkflowOrchestration - Development Excellence Methodology
Auto-loaded for development work. This skill enforces rigorous development methodology that eliminates common failure modes and maximizes code quality.
Core Philosophy
High-quality software comes from disciplined process, not heroic effort. This methodology prevents the most common development failures:
- Starting implementation before understanding the problem (Plan Mode Default)
- Thrashing in a broken state instead of re-planning (Stop & Re-plan)
- Working in a cluttered context window (Subagent Strategy)
- Repeating the same mistakes (Self-Improvement Loop)
- Claiming completion without proof (Verification Before Done)
- Accepting hacky solutions when elegant ones exist (Demand Elegance)
- Waiting for hand-holding on obvious fixes (Autonomous Bug Fixing)
1. Plan Mode Default
CRITICAL: Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
When to Plan
Enter plan mode when ANY of these are true:
- Task requires 3+ distinct steps
- Architectural decisions need to be made
- Multiple files/components will be affected
- User says "plan first" or requests a plan
- You're not 100% certain about the approach
- Something went sideways (stop immediately, don't push forward)
Planning Process
# 1. Write detailed plan to task file
# Location: ~/Nextcloud/PAI/tasks/todo.md
# 2. Plan structure (required sections):
# - OBJECTIVE: What are we building/fixing?
# - CONTEXT: What's the current state?
# - CONSTRAINTS: What limitations exist?
# - APPROACH: High-level strategy
# - STEPS: Numbered checklist items [ ]
# - VERIFICATION: How will we prove it works?
# - ROLLBACK: How to undo if things break?
# 3. Check in with user BEFORE starting implementation
# Present the plan, wait for approval
# 4. Track progress as you work
# Mark items complete: [x] in todo.md
# 5. Explain changes at each step
# Add high-level summary after each major step
# 6. Document results
# Add REVIEW section to todo.md with:
# - What worked
# - What didn't
# - Lessons learned
# - Final verification results
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 838 lines · 73 tokens per session scan B 59f824b95e84
workflow-orchestration is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 5,784 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
channels-setup
Use when a developer wants to build their first CopilotKit Channels agent and get it answering in Slack or Microsoft Teams — "set up a channel", "connect my agent to Slack", "get my agent into Teams", or starting from nothing and wanting a working channel end to end. Covers the whole path: inspecting or scaffolding…
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
gmail-trigger
Beta. Act on new Gmail as it arrives: get pinged only for urgent mail, digest newsletters, forward invoices — any standing instruction, across one or several accounts.
watcher
Create and manage polling watchers that monitor external services (Gmail, Google Calendar, GitHub, Linear, Outlook) for events and process them with custom action prompts.
tmux
Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).