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/notifying-main-agent)<a href="https://agentmods.dev/skills/wayne930242/straw-boss/notifying-main-agent"><img src="https://agentmods.dev/badge/skills/wayne930242/straw-boss/notifying-main-agent.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.1 | $0.00022 | $0.00463 |
| Opus 5 | $0.00011 | $0.00231 |
| Sonnet 5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
notifying-main-agent 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 8d 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
Overview
A Herdr-launched session is an independent agent. Discuss work details and authorization directly with the user; the main agent accepts those decisions. Ask it only for integrated context or a coordinator-owned action result. Address every operation by your instruction path.
Live bodies are delta-only and at most two sentences. Put detailed context or
evidence in repeatable --ref; transport adds identity, intent, and correlation.
Ask the main agent
uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/send-dispatch-message.py" \
--instruction-path <your exact instruction path> \
--to main --intent question \
--message "<one integration question; include expected reply shape>" \
--ref "<source or artifact when needed>"
Continue independent work. If the coordinator's answer becomes blocking, report
awaiting-main-agent; a user-owned question remains awaiting-user-input.
Report status
At every checkpoint and terminal outcome, make exactly one call:
uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/report-task-status.py" \
--instruction-path <your exact instruction path> \
--status <done|failed|awaiting-authorization|awaiting-user-input|awaiting-main-agent> \
--note "<outcome or exact unblock>" --ref "<proof when needed>"
For done and failed, the command writes first and then notifies the recorded
main-agent Herdr endpoint. Delivery failure is surfaced and leaves durable state
for watcher recovery.
Report a feature-branch push
uv run --script "${CLAUDE_PLUGIN_ROOT}/scripts/send-dispatch-message.py" \
--instruction-path <your exact instruction path> \
--to main --intent inform \
--message "Pushed <branch>; continuing." --ref "<MR/PR>"
If no live endpoint exists, record the same detail with report-progress.py.
Continue immediately.
Complete when: the intended message was delivered, or terminal status was persisted and its Herdr notification succeeded or visibly failed.
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.
- 8d ago First seen · 58 lines · 22 tokens per session scan A f49ab0cc5393
notifying-main-agent is a skill published in the GitHub repository wayne930242/straw-boss (3 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 463 once invoked, about $0.0001 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
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
remind
A correction helper that checks which project rules or required steps were missed and loads the relevant guidance.
adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/ /adr- - .md with a 3-digit zero-padded number. Handles the Superseded case: bidirectional linking when a new ADR replaces an old one. Use when: recording why an architectural…