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/giggsoinc/raven/agent-chainingnpx skills add giggsoinc/raven --skill agent-chaininggit clone --depth 1 https://github.com/giggsoinc/ravenWrote 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/giggsoinc/raven/agent-chaining)<a href="https://agentmods.dev/skills/giggsoinc/raven/agent-chaining"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/agent-chaining.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.00050 | $0.01028 |
| Opus 5 | $0.00025 | $0.00514 |
| Sonnet 5 | $0.00010 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
agent-chaining 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Chaining Specialist
Domain: Multi-Agent Systems · Orchestration · Context Management · Subagent Design
Pre-flight — ask before designing any chain
- What problem actually requires multiple agents? → single agent first, always
- Sequential or parallel? → depends on step dependencies
- What's the token budget? → each subagent call costs tokens
- What are the failure modes? → what happens if a subagent fails mid-chain?
- Where does shared state live? → agents don't share memory
Rule: If one agent with the right tools can do it → don't chain. Chaining adds latency, cost, and failure surface. Justify it.
When to chain vs not
| Chain when... | Don't chain when... |
|---|---|
| Work can run in parallel | Single-domain task |
| Specialist isolation needed | Tightly sequential, no parallelism |
| Context window exceeded | Shared mutable state needed |
| Independent verification needed | Low latency requirement |
| Long-running background work | You're adding complexity for no gain |
Spawning — the critical rules
Subagent has NO memory of the parent conversation. The prompt must be fully self-contained.
Every subagent prompt must include:
- Goal in the first sentence
- Absolute file paths — no relative references
- What you've already done / ruled out
- Expected output form
- Scope cap — "only look at src/api/, not tests/"
- Failure instruction — "if X not found, report that, don't guess"
Parallel: send multiple agent calls in a single message — they run concurrently. Never send independent agents sequentially — doubles latency for no reason.
Background: for long-running tasks where the parent has other work to do. Parent continues; notified when subagent completes.
Context passing — 3 patterns
- Self-contained prompt — include all context inline. Best default.
- File handoff — orchestrator writes to a temp file; subagent reads it. Good for large context. Bad for parallel agents that might conflict.
- Summary handoff — orchestrator compresses Phase 1; subagent gets the summary. Good for sequential chains.
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 · 135 lines · 50 tokens per session scan A f5f677ab75a6
agent-chaining is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 1,028 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…