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 agentmods add skills/wcgomes/agents-workspace/orchestratenpx skills add wcgomes/agents-workspace --skill orchestrategit clone --depth 1 https://github.com/wcgomes/agents-workspaceWrote 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/wcgomes/agents-workspace/orchestrate)<a href="https://agentmods.dev/skills/wcgomes/agents-workspace/orchestrate"><img src="https://agentmods.dev/badge/skills/wcgomes/agents-workspace/orchestrate.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 | $0.00067 | $0.05101 |
| Opus 5 | $0.00034 | $0.02550 |
| Sonnet 5 | $0.00013 | $0.01020 |
| Haiku 4.5 | $0.00007 | $0.00510 |
Grade A, and why
orchestrate 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 319 lines · 67 tokens per session scan A 4b669fac779a
orchestrate is a skill published in the GitHub repository wcgomes/agents-workspace (9 stars, last pushed 9d ago), with no licence file. It adds 67 tokens to every session and 5,101 once invoked, about $0.0003 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-31.
Other skills, from other repositories
hyperbrief
Use AFTER hyperbrief-trigger-check returns FULLHYPERBRIEF, SUMMARYBRIEF, DEEPBRIEF, or MINIMALBRIEF. v0.9 adds the request tier (Hyperbrief.md §2.6) — a bare request for a brief is a SUMMARYBRIEF rather than the heaviest tier, and DEEPBRIEF (§0.6) is request-only and the only tier permitted to fan out, so an unnamed…
ultrasafe-synthesizer
Pre-release security testing — retire-barrier fan-out sink. Aggregate the 7 attacker agents' findings (ai-llm / web-api / supply-chain / crypto / social-eng / methodology / threat-model) via BFT quorum 2f+1 cross-axis confirmation, diversity-enforced source independence (perspective × prompttemplatehash × seed 3-tuple…
ultrasafe-crypto-reviewer
Pre-release simulated penetration testing from the cryptography attacker perspective — key management / random source / TLS misuse / signature scheme / constant-time violation / PQC readiness / cryptographic agility envelope. Triggered by Ultrasafe orchestrator (ultrasaferunfanout MCP tool) when the axis-set includes…
ultrasafe-methodology-compliance
Use BEFORE a publish-equivalent release (npm publish / pip upload / git push --tags to public) — Ultrasafe 8-agent fan-out 의 Methodology / Compliance attacker 시각. Test methodology gap · coverage cliff · compliance catalog (NIST 800-115 / OSSTMM / OWASP WSTG / PTES / ISO 27001:2022 / CIS v8.1) 의 16-cell 2D dispatch…
ultrasafe-social-engineer
Pre-release security testing — simulated penetration from the social-engineering / human-factor attacker perspective. Use when the Ultrasafe orchestrator dispatches Agent 5 of the 8-agent fan-out at iteration N (usf-social-eng axis 포함 시), or when a publish-equivalent command triggers the PreToolUse hook and the…
ultrasafe-supply-chain-auditor
Pre-release simulated penetration testing from the dependency / SBOM / typosquatting / signing-chain perspective. Invoke as Agent 3 of the Ultrasafe 8-agent fan-out (Ultrasafe.md §15.3) whenever the iteration axis-set includes usf-supply-chain, or whenever a release candidate touches dependency manifests (package.json…