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/hecer/yoke/yoke-workflownpx skills add HECer/yoke --skill yoke-workflowgit clone --depth 1 https://github.com/HECer/yokeWrote 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/hecer/yoke/yoke-workflow)<a href="https://agentmods.dev/skills/hecer/yoke/yoke-workflow"><img src="https://agentmods.dev/badge/skills/hecer/yoke/yoke-workflow.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.00037 | $0.00451 |
| Opus 5 | $0.00018 | $0.00226 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
yoke-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 5d 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
Yoke Workflow
Provide the same interaction contract in Claude, Codex, and Gemini.
- Read
.yoke/config.yaml. If it is missing, offeryoke setup . --host=<current-agent>and run the setup flow before planning. - Plan before starting the loop. Inspect the project, then ask one focused question at a time only where the answer changes product behavior, scope, architecture, security, data ownership, external cost, or an irreversible choice. Include a recommended answer. Resolve routine implementation details yourself.
- Summarize the agreed design in
.yoke/plan.md, including goals, non-goals, constraints, and decisions. Use theauthoring-prdskill to turn it into small stories with testable acceptance criteria. Runyoke prd check .. - Ask once for approval of the complete plan and story set. Do not begin implementation before that approval.
- If
loop.enabledis true, run the stories without routine follow-up questions using the configured runner. Preferyoke loop run . --max=5 --isolate, report status after each batch, and continue until complete or genuinely blocked. - Respect
loop.decisionPolicy:auto: choose the most suitable option from the plan, current code, and established conventions. Record the interpretation and continue.critical: routine ambiguity is still resolved automatically. If the loop reports a pending critical decision, runyoke loop decision ., present its options and recommendation to the user, ask exactly that question, then runyoke loop answer . --choice=<id> --rationale="<answer>". The answer command records the decision and resumes the same story.
- Never ask whether to run tests, review, commit, or continue to the next approved story. Those are part of the approved workflow.
The user's configured commit identity is authoritative. Do not add an AI co-author unless commit.allowCoAuthors explicitly permits it.
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.
- 5d ago First seen · 21 lines · 37 tokens per session scan A a0cfd9fd7ed0
yoke-workflow is a skill published in the GitHub repository HECer/yoke (2 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 451 once invoked, about $0.0002 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
add-new-agent-support
Add a new agent (tool) support to agent-command-sync following the registry pattern.
standard-skill
A standard test skill for Gemini.
with-config
A Codex skill with openai.yaml configuration.
test-skill
A test skill for chimera.
basic-skill
A basic test skill for Claude.
unity-vrc-skills-renovator
VRChat skill renovator for knowledge fill, refresh, and quality improvement. Use this skill when updating VRChat skills to new SDK versions, filling missing knowledge, fixing outdated information, or improving skill quality. Targets unity-vrc-udon-sharp and unity-vrc-world-sdk-3 skills. Triggers on: update skills, SDK…