Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Fast Subagent

ASecurity

Use for any routine/checkable step — summarize, extract, classify, reformat, draft boilerplate, first pass over a file — every such step, all session. Sends to the router's fast-subagent role, which picks backend/fallback. Names no model ids.

3 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgobashapidatabasebackend

Works with

cliapi

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/23/2026

$npx -y skills add dryvist/claude-code-plugins --skill fast-subagent --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fast Subagent?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Fast Subagent
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dryvist-fast-subagent/badge)](https://www.skillsdirectory.com/skills/dryvist-fast-subagent)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: fast-subagent
description: Use for any routine/checkable step — summarize, extract, classify, reformat, draft boilerplate, first pass over a file — every such step, all session. Sends to the router's fast-subagent role, which picks backend/fallback. Names no model ids.
license: MIT
metadata:
  version: 1.0.0
  author: dryvist homelab
  hermes:
    category: research
    tags:
      - delegation
      - routing
      - cost
      - local
    related_skills:
      - local-subagents
      - premium-agent-orchestration
---

# fast-subagent

Doctrine: `local-subagents` (same plugin) says *why* and *what* to delegate and
how a busy single-slot tier behaves. This skill is the one-command *how*, tuned
for reuse: call it early, call it often, call it again.

## 1. When — every routine step, all session long

The Delegate column of `local-subagents` §1 is the list. The habit this skill
adds: **do not decide once**. Each time a new routine step appears — the fifth
log to reduce, the third file to summarize, the test output to read — send it
the same way. Repeated calls from one harness keep the backend's prompt cache
warm and the lock held, so the tenth call is cheaper than the first.

Keep for yourself: intent, architecture, tradeoffs, risk, anything you would
not accept from a smaller model without checking. Never send secrets, secret
store context, private topology, or personal data.

## 2. How — one command

```sh
printf '%s\n' "$INSTRUCTION" "$INPUT" | fast-subagent.sh
```

`fast-subagent.sh` lives in this skill's `scripts/` directory (resolve it
relative to this file; it needs only `bash`, `curl`, `jq`). It reads the
endpoint from the environment — `LLM_ROUTER_URL` + `LLM_ROUTER_TOKEN_FILE`, or
the local proxy's `OPENAI_API_BASE_URL` + `LITELLM_LOCAL_KEY` — sends one
bounded request for role `fast`, prints the answer on stdout and
`model=<what answered> fallbacks=<n>` on stderr.

Options: `--model subagent` (the alias), `--system TEXT`, `--max-tokens N`,
`--timeout SEC`, `--raw` (full JSON), `--release` (see §4).

Write the prompt for a small model — short imperatives, an explicit output
shape, a row cap, a hard STOP:

```text
Extract every failing test from the input. Do not explain or fix.
Output ONLY: test name | file | first error line. At most 40 rows. STOP.
```

Send only what the step needs. A call that carries your whole transcript costs
more than doing the step yourself.

## 3. What the router decides, not you

`fast` is a role whose target and fallback order live in the router's own
database and are edited in its admin UI — the operator can reorder or retarget
the chain at any time without a converge, a rebuild, or a change to this skill.
So: never name a physical model, never assume which backend answered, and read
`model=` on stderr when it matters. `fallbacks=1` or more means the first rung
was busy and the router moved on; that is the chain working, not an error.

## 4. When it says no

| Exit | Meaning | Do |
| --- | --- | --- |
| 2 | No endpoint in the environment | Do the step yourself and say so. Do not look for a provider key. |
| 3 | `401`/`403` | Report it. Never retry with a different credential. |
| 4 | Still busy after one `Retry-After` wait | Do the step yourself or pick another entry from `local-subagents` §3, and say which. Do not loop. |
| 5 | Transport or request failure | Report the message; a `400` naming an unknown model means the role is not seeded on this router yet. |
| 7 | `200` but no text (budget spent on reasoning, `finish_reason=length`) | Retry once with a higher `--max-tokens`; never treat empty output as an answer. |

`--release` on your **last** call of a burst frees the single-slot backend for
the next caller instead of waiting for the lock's own timeout. It is a
courtesy: the timeout is what guarantees release, so never depend on it.

## 5. Report what you used

Name the role and, when the reader needs it, the `model=` line, for each
delegated result. Say when you fell back to doing the step yourself.

## Related skills

- **local-subagents** (ai-delegation) — the full delegation doctrine, the live
  model menu, the fast-subagent tier contract.
- **premium-agent-orchestration** (ai-delegation) — which decisions a premium
  session keeps.
- **delegate-to-ai** (ai-delegation) — routing to another harness or CLI.

Attribution

dryvistdryvist
View sourceSee grades on GitHubMore from dryvist →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →