Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add wayne930242/straw-boss/plugin install straw-bossWrote 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/wayne930242/straw-boss/bringing-coworker)<a href="https://agentmods.dev/skills/wayne930242/straw-boss/bringing-coworker"><img src="https://agentmods.dev/badge/skills/wayne930242/straw-boss/bringing-coworker/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/wayne930242/straw-boss/bringing-coworker"><img src="https://agentmods.dev/badge/skills/wayne930242/straw-boss/bringing-coworker.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.00051 | $0.00469 |
| Opus 5 | $0.00026 | $0.00234 |
| Sonnet 5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
bringing-coworker 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 10d 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
Bring a coworker
1. Scope the second opinion
Give the coworker one outcome that can run beside your current task. Default to
review-only. A writing task names a disjoint repo-relative --writable-path
scope.
Complete when the task is independently useful and its write scope is disjoint.
2. Start beside you
Use your canonical instruction path from the dispatch contract:
uv run --script "$HOME/.straw-boss/bin/run-straw-boss-script.py" \
--origin-root "${CLAUDE_PLUGIN_ROOT:-$PWD}" --prefer-installed \
--script dispatch-coworker.py -- \
--parent-instruction-path <your-instruction-path> \
--slug <unique-slug> [--name <short-name>] \
--agent-kind claude|codex --task "<user requirement and integrated context>" \
[--writable-path <repo-relative-path>]...
The command authenticates your session, opens the coworker in this tab and
worktree, injects its contract, and confirms delivery. Omit --name for a
<app>-coworker handle derived automatically. Complete when it returns the
coworker's pane and instruction path.
3. Work with the user
Point the user to the coworker pane. The coworker and user decide feedback and choose the specification, design, implementation, and the verification method inside the anchor you scoped for it; continue on your disjoint scope.
Complete when the coworker reports done or failed; parent and root
coordinator receive that terminal event automatically.
4. Integrate and close
Review the reported result, integrate the conclusion, close only the coworker
pane, then run wrap-up-task.py --app <app> --slug <slug>. The shared tab and
your own instruction remain active.
Complete when the pane is closed and the coworker instruction is archived.
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.
- 10d ago First seen · 51 lines · 51 tokens per session scan A 71e3aa5ae134
bringing-coworker is a skill published in the GitHub repository wayne930242/straw-boss (4 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 469 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
post-dev-recap
Post-development recap wrapper. Use when: AI/Codex just finished implementing a feature and the user wants a guided walkthrough with scope detection + doc generation + follow-up Q&A. Not for: generating only a doc (use /recap-doc), Q&A over an existing recap (use /recap-ask), technical share-out (use /tech-brief)…
obsidian-cli
Obsidian vault integration via official CLI. Use when: capturing dev artifacts to Obsidian vault, searching vault for context, appending to daily note, managing tasks in vault. Not for: general note-taking without Obsidian (use regular files), browsing Obsidian docs (use agent-browser). Output: vault search results…
statusline-config
Customize Claude Code statusline. Use when: user says 'statusline', 'status line', 'customize statusline', 'modify statusline', 'statusline settings', 'statusline theme', 'change theme', 'color scheme', wants to add/remove/change segments (cost, git, model, context), switch color themes (catppuccin, dracula, nord), or…
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
sys-configure
Configure Claude Octopus — redirects to /octo:setup interactive wizard.