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 yptang98/CostMarshal --skill orchestrate-cost-aware-agentsgit clone --depth 1 https://github.com/yptang98/CostMarshalWrote 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/yptang98/costmarshal/orchestrate-cost-aware-agents)<a href="https://agentmods.dev/skills/yptang98/costmarshal/orchestrate-cost-aware-agents"><img src="https://agentmods.dev/badge/skills/yptang98/costmarshal/orchestrate-cost-aware-agents/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/yptang98/costmarshal/orchestrate-cost-aware-agents"><img src="https://agentmods.dev/badge/skills/yptang98/costmarshal/orchestrate-cost-aware-agents.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.00161 | $0.02003 |
| Opus 5 | $0.00081 | $0.01001 |
| Sonnet 5 | $0.00032 | $0.00401 |
| Haiku 4.5 | $0.00016 | $0.00200 |
Grade A, and why
orchestrate-cost-aware-agents 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 11d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate cost-aware agents
Treat this as the Codex-native product entry point. Keep Python and CLI commands as internal implementation and diagnostic details unless the user explicitly asks for them.
Before taking task actions, read ../../SKILL.md completely
and follow its scheduler, safety, evidence, recovery, budget, and ArchMarshal
compatibility requirements. Resolve every relative script or reference path
from the plugin root, two directories above this file.
Interact with the user in Codex: translate natural-language intent into the bounded CostMarshal workflow, report durable outcomes, and expose a manual command only when recovery or diagnosis genuinely requires it.
Natural-language control plane
Classify the user's request before running the internal engine:
- Set up CostMarshal: discover an existing CostMarshal project first,
including compatible v2 state. If none exists,
obtain only the missing objective, writable workspace, reviewed low/medium/high
provider catalog, budget, and governance choice. Preview provider/profile
changes before applying them, never request secret values in chat, then run
initwith a stable project name. - Plan or explain: use
providers,budget, and read-onlyroute. Explain the safety floor, complete admitted chain, per-step reservation, historical acceptance evidence, and why a cheaper route was rejected. Do not create a task or start a provider. - Do new work: inspect
status,work-graph, and relevantmodel-memoryscopes. Decompose the request into bounded work packages with roles, dependencies, deliverables, gates, and teaching policy. Create each package withnew-task, run a read-only route explanation, thendispatch --startonly when its dependencies are accepted and it remains within the user's workspace, budget, paths, capabilities, and acceptance criteria. Start the scheduler in bounded cycles and stop monitoring only at gated leader acceptance, explicit failure, budget exhaustion, a recoverable pause, or user stop. For legitimately low-floor, text-only analysis, debugging proposals, and scout/reviewer packages routed to LongCat, prefer report-onlyproposal-api: send committed allowlisted context, grant no writes or tools, and require Codex Leader review. Do not relabel a medium/high-risk task merely to force a cheaper tier. A severity-0/1 defect may receive one precise feedback retry; otherwise continue to the admitted Codex Worker or let the Codex Leader implement. Treatlow/medium/highas cost/safety routing authority, never as a fixed intelligence ranking. - Coordinate a large project: inspect
repositoriesandworkstreamsbefore task creation. Register only explicit committed Git roots, bind each task to one repository and optional Workstream, and respect Workstream dependencies, concurrency, and CNY allocations. At a milestone, freeze a complete staged integration plan and request a Leader Gate; never claim cross-repository atomicity or mutate source repositories while planning. - Audit or monitor: use JSON
status,dashboard,work-graph,workstreams,repositories,production-status,model-memory,providers,budget,validate, and read-onlygovernance-status. Summarize dependency readiness, integration Gates, evaluations, errors, cost, and any unpromoted policy candidate; never infer success only from a live process. - Check Codex compatibility: use
codex-native-statusbefore diagnosing native child-agent or App Server availability. This probe makes no provider call. A failed handshake disables only the native attempt team and preserves the original single-agent execution contract; it never authorizes a provider, isolation, credential, or safety fallback. - Resume or recover: run
recoverread-only first. Show the exact restart plan before--restart-missing; preserve sealed routes, generations, attempts, reservations, runtime receipts, and leader ownership. Never silently respawn an uncertain actor. - Stop: use the actor's durable identity with
stop-actor --stop-runtime, then verify terminal state and cleanup receipts. Do not kill by an unverified PID or process name.
What ships with it
1 file 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.
- 11d ago First seen · 152 lines · 161 tokens per session scan A 276c7290e0d8
orchestrate-cost-aware-agents is a skill published in the GitHub repository yptang98/CostMarshal (4 stars, last pushed 1mo ago), licensed MIT. It adds 161 tokens to every session and 2,003 once invoked, about $0.0008 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
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
beevibe-use-repo
You are the child agent inside a fresh Docker sandbox. Borrow the given GitHub repo, produce a real artifact for the goal, and export it. Do not review the repo. The proof is that it works.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
beevibe-discover-repo
Find the best GitHub repo for a goal, then call userepo to run it in a sandbox. Use whenever the user's goal requires a capability you don't have natively and you haven't been given a specific repo.
board-pilot
Generic, board-driven implementation pipeline: polls a GitHub Project on a schedule, ARMS an item the moment a human drags it into the configured trigger column, then advances it one stage per tick — each stage a Bridge primitive (skill / workflow / agent / cmd) — and STOPS at a human-gated draft PR. The engine is…
bridge-overlay
Subscribe a Bridge to an ORG OVERLAY — a git repo an organisation publishes that ships its shared config (contexts, projects, mandants, accounts, org skills/agents/standing-orders, an ecosystem fragment) as a flat mirror tree. /overlay add sparse-clones the overlay, validates its manifest, previews a per-file plan…