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 sefaertunc/Worclaude --skill subagent-usagegit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/sefaertunc/worclaude/subagent-usage)<a href="https://agentmods.dev/skills/sefaertunc/worclaude/subagent-usage"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/subagent-usage/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/sefaertunc/worclaude/subagent-usage"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/subagent-usage.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.00016 | $0.01255 |
| Opus 5.5 | $0.00006 | $0.00502 |
| Sonnet 5.5 | $0.00003 | $0.00251 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade A, and why
subagent-usage 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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent Usage
What Subagents Are
Subagents are separate Claude instances spawned from your main session. They have their own context window, execute independently, and return results to the main session. Your main context stays clean.
When Subagents Help
Tasks that benefit from subagents:
- Testing: writing tests for code you just implemented (test-writer agent)
- Code review: reviewing your own changes for quality (code-simplifier agent)
- Research: reading many files to answer a specific question
- Parallel work: running verification while you continue designing
- Build validation: checking that everything compiles and passes (build-validator)
- File generation: creating boilerplate, configs, or template files
The common thread: these tasks require context (reading files, understanding code) but that context doesn't need to persist in your main session.
When NOT to Use Subagents
- Tasks requiring back-and-forth with the user (subagents can't interact with users)
- Tasks where the result needs deep integration with your current reasoning
- Very small tasks (the overhead of spawning isn't worth it)
- Tasks that depend on conversation history the subagent doesn't have
Context Hygiene
Your main session has limited context. Every file you read, every long output you generate, consumes context. Subagents let you offload this:
Instead of:
- Read 10 test files to understand patterns (consumes context)
- Write new tests (uses that context)
- Continue main work (context is now polluted with test details)
Do:
- Spawn test-writer subagent with: "write tests for src/merger.js following patterns in tests/core/"
- Continue main work while subagent works
- Subagent returns: "wrote 3 test files, all passing"
- Main context stays clean
Parallel vs Sequential Subagents
Parallel: when tasks are independent.
- Run test-writer and code-simplifier on different parts of the code simultaneously
- Run build-validator while continuing implementation
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.
- 1mo ago First seen · 132 lines · 16 tokens per session scan A f5e106eb2188
subagent-usage is a skill published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,255 once invoked, about $0.0001 per session on Opus 5.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
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.