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 Tarekkharsa/agentstack --skill orchestrate-workflowgit clone --depth 1 https://github.com/Tarekkharsa/agentstackWrote 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/tarekkharsa/agentstack/orchestrate-workflow)<a href="https://agentmods.dev/skills/tarekkharsa/agentstack/orchestrate-workflow"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/orchestrate-workflow/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/tarekkharsa/agentstack/orchestrate-workflow"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/orchestrate-workflow.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.00080 | $0.01118 |
| Opus 5.5 | $0.00032 | $0.00447 |
| Sonnet 5.5 | $0.00016 | $0.00224 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
orchestrate-workflow 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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate a governed multi-agent workflow
Use when you want the Bun-in-Rust shape — an implementer writes, independent adversarial reviewers attack the diff, a fixer applies feedback — with each agent's capabilities, model, and secrets managed by agentstack instead of hand-assembled per run.
The division of labor is fixed: an executor runs the loop (sandcastle, Claude Code workflows, your own script); agentstack defines and provisions the agents the loop spawns. Don't blur it in either direction.
1 — Define roles as profiles
A role is a profile: which skills, which servers, and (by convention) which
model. In .agentstack/agentstack.toml:
[profiles.implementer]
skills = ["porting-guide"] # the task's context artifacts
servers = ["github"]
[profiles.reviewer]
skills = ["adversarial-review"] # ships in this catalog
servers = [] # reviewers judge the diff; no tools needed
Keep reviewer profiles minimal on purpose — a reviewer with no servers can't be tool-poisoned, and the diff is all it should trust anyway.
2 — Bind models to roles
Pick per role, not per run: bulk/mechanical implementation → a cheap strong
coder; review → a different model family than the implementer when possible
(diverse failure modes). Record the binding wherever the executor configures
each agent (sandcastle's agent: option, a Workflow model: param, a
--model flag). If the route-by-cost skill is loaded, apply its ladder.
3 — Provision the sandbox (works today, no extra tooling)
The box needs three things: the harness CLIs, the rendered capabilities, and secrets that never touch disk.
# on the host — render the role's capabilities into the worktree the
# sandbox will mount (repeat per worktree):
cd <worktree> && agentstack use implementer --write
# start the container with secrets injected from the keychain at run time —
# no .env file, nothing baked into the image or committed:
docker run \
-e GH_PAT="$(agentstack secret get GH_PAT)" \
-e ANTHROPIC_API_KEY="$(agentstack secret get ANTHROPIC_API_KEY)" \
-v <worktree>:/work ...
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.
- 1mo ago First seen · 108 lines · 80 tokens per session scan A 4dc405376b95
orchestrate-workflow is a skill published in the GitHub repository Tarekkharsa/agentstack (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 1,118 once invoked, about $0.0003 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-31.
Other skills, from other repositories
terraform-setup
Install (deploy) MCP Gateway & Registry on AWS using the Terraform aws-ecs stack (ECS Fargate, Aurora, DocumentDB, Keycloak). Asks whether you are running from an EC2 instance or a local laptop, confirms the required AWS IAM permissions are in place, clones the repository, bootstraps the toolchain (uv, AWS CLI…
macos-setup
Complete macOS setup and teardown for MCP Gateway & Registry (AI-registry). Clones the repository, installs all services, configures Keycloak auth, registers the Cloudflare docs server, and verifies the full stack. Also supports complete teardown. Can be run directly from its GitHub URL without the repository already…
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
pr-review
Review a GitHub pull request using multiple expert personas. Takes a PR URL as input, analyzes the changes, and generates comprehensive review feedback from different perspectives (Merge Specialist, Frontend, Backend, Security, DevOps, AI/Agent, SRE, Chief Architect).
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
writing
Write prose people will actually read. Use for any prose you produce - docs, READMEs, release notes, blog posts, PR descriptions, issue text, commit bodies, design docs, emails, chat answers. Applies Orwell's six rules and strips the LLM tells - passive voice, dead metaphors, and -ly padding.