bytedance/agentkit-samples is a collection of examples and tutorials for Volcengine AgentKit, an AI-agent development platform for building, deploying, and operating agent applications. Developers use the samples to learn agent creation, multi-agent collaboration, memory, retrieval, MCP integrations, media generation, customer service, and other workflows. The catalogue skills provide agent workflows based on these examples.
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 bytedance/agentkit-samples --skill byted-util-volcengine-detect-retrygit clone --depth 1 https://github.com/bytedance/agentkit-samplesWrote 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/bytedance/agentkit-samples/byted-util-volcengine-detect-retry)<a href="https://agentmods.dev/skills/bytedance/agentkit-samples/byted-util-volcengine-detect-retry"><img src="https://agentmods.dev/badge/skills/bytedance/agentkit-samples/byted-util-volcengine-detect-retry/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/bytedance/agentkit-samples/byted-util-volcengine-detect-retry"><img src="https://agentmods.dev/badge/skills/bytedance/agentkit-samples/byted-util-volcengine-detect-retry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00101 | $0.02746 |
| Opus 5 | $0.00051 | $0.01373 |
| Sonnet 5 | $0.00020 | $0.00549 |
| Haiku 4.5 | $0.00010 | $0.00275 |
Grade A, and why
byted-util-volcengine-detect-retry 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 6d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volcengine Detect Retry
Reduce Volcengine Cloud Detect (云拨测) operations toil. This skill confirms whether a failing dial point is a real outage or just noise, and — when a dial point itself is broken — suggests a similar replacement node.
This skill ships no script of its own. It is pure orchestration: every action is one of
the byted-util-volcengine-cloud-detect skill's volc_detect.py CLI commands
(get-task, get-result, list-nodes, fuzzy-search-nodes, create-task, delete-task).
Follow the workflow below by invoking those commands in sequence and applying the decision
logic to their JSON output.
Requires: byted-util-volcengine-cloud-detect skill. Do not reimplement any Cloud Detect API call here.
Locate The Base CLI
Resolve volc_detect.py dynamically (never hard-code an absolute path):
VOLC_DETECT="${VOLC_DETECT:-$(find "${SKILLS_DIR:-$HOME/Code/Skill}" -type f \
-path '*/byted-util-volcengine-cloud-detect/scripts/volc_detect.py' 2>/dev/null | head -n 1)}"
test -n "$VOLC_DETECT" || { echo "volc_detect.py not found"; exit 1; }
alias vd="python3 \"$VOLC_DETECT\""
All commands below are written as python3 "$VOLC_DETECT" <command>.
Prerequisites
Volcengine credentials must be present (the base skill enforces this). If either is missing, follow the base skill's Prerequisites section to collect and persist them:
test -n "$VOLC_ACCESSKEY" && test -n "$VOLC_SECRETKEY"
Decision Logic
For each dial point whose latest sample in the scan window failed:
- Retry 5 times (configurable) against the same monitored target via a temporary
create-task.- All retries succeed → transient glitch → ignore (
transient_issue). - Any retry fails → go to control validation.
- All retries succeed → transient glitch → ignore (
- Control validation: a temporary
create-taskdials a trusted domain from the same node.- China nodes →
https://cn.bing.com - Overseas nodes →
https://www.google.com - Control succeeds →
real_failure(target is genuinely down for that node) → ALERT. - Control fails →
node_issue(the dial point itself is broken) → find similar replacement nodes and suggest replacing it.
- China nodes →
- Temporary retry/control tasks are always deleted (
delete-task).
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.
- 6d ago First seen · 241 lines · 101 tokens per session scan A 8d37d59772dd
byted-util-volcengine-detect-retry is a skill published in the GitHub repository bytedance/agentkit-samples (450 stars, last pushed 5d ago), licensed Apache-2.0. It adds 101 tokens to every session and 2,746 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
adk-debug
Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…
claw-admin
Claw system administration: service management, IM connections, logs, cron, and workspace diagnostics. Use when the user asks to manage claw services, connect/disconnect IM platforms, view logs, or perform system-wide operations.
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
optimize
Review code for efficiency and performance. Triggered by "/optimize" when user wants to identify bottlenecks or improve performance.
golang-troubleshooting
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production…