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 VincentChuWaiChow/vanguard-frontier-agentic --skill agentic-delegationgit clone --depth 1 https://github.com/VincentChuWaiChow/vanguard-frontier-agenticWrote 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/vincentchuwaichow/vanguard-frontier-agentic/agentic-delegation)<a href="https://agentmods.dev/skills/vincentchuwaichow/vanguard-frontier-agentic/agentic-delegation"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/agentic-delegation/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/vincentchuwaichow/vanguard-frontier-agentic/agentic-delegation"><img src="https://agentmods.dev/badge/skills/vincentchuwaichow/vanguard-frontier-agentic/agentic-delegation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 34 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 69 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 114 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00060 | $0.01545 |
| Opus 5 | $0.00030 | $0.00772 |
| Sonnet 5 | $0.00012 | $0.00309 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
agentic-delegation 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 11d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Delegation
Doctrine
Most tasks in this repo decompose into cheap, parallelizable work plus a small amount of work that genuinely needs the orchestrator's judgment. Default to delegating the former. Before doing multi-step work yourself, ask: can a cheaper model do this step just as well?
a) Exploration and reconnaissance → Haiku
- Use the
Exploreagent type withmodel: haikufor read-only reconnaissance: locating files, grepping for symbols, mapping call sites, summarizing existing structure. - Scope each Explore task tightly — one question, one area of the tree. Do not send an Explore agent an open-ended "understand the whole system" ask; split it into targeted sweeps instead.
- Require file:line citations in every finding. A report without exact paths and line numbers is not actionable — re-run it with a tighter prompt rather than accepting it.
b) Bulk writing → Sonnet
- Route bulk writing — docs, guides, boilerplate, test scaffolding, repetitive multi-file edits — to Sonnet subagents.
- Give each writing task a precise spec: exact file paths to create or edit, the content shape expected, and which repo conventions to mirror (frontmatter shape, heading structure, existing tone).
- Hard-constrain every writing delegate:
- Files it may touch — list them explicitly; nothing outside that list.
- Linters/gates it must pass — e.g.
npx markdownlint-cli2,codespell, or the schema/validation gate relevant to the files it is touching. - No commits — delegates write files; only the orchestrator commits.
Orchestrator requirements
- Haiku must never be the orchestrator. It explores and runs gates; it does not plan, decompose, or accept work.
- When Sonnet is the orchestrator, run it at high reasoning effort at minimum — use the harness's maximum-thinking mode where available. Planning and delegation quality degrade below that, and a weak plan wastes every delegate downstream.
- The model split in this skill is unchanged by who orchestrates: even a Sonnet orchestrator routes bulk writing to Sonnet subagents — the benefit is keeping the orchestrator's context clean for judgment, not just the per-token price.
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.
- 11d ago First seen · 126 lines · 60 tokens per session scan A 2eae965eeb63
agentic-delegation is a skill published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,545 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-30.
Other skills, from other repositories
telegram
The only Telegram skill your AI agent needs. Read messages, parse channels, download and transcribe voice notes — all via Telethon user API. One session file, zero bots. Use when user says 'read telegram', 'check saved messages', 'fetch from telegram', 'parse channel', 'transcribe voice', 'telegram search', 'check my…
RcppParallel
R RcppParallel package for parallel C++. Use for multi-threaded C++ code with Intel TBB.
limma
R limma package for microarray and RNA-seq. Use for linear models in differential expression.
r-parallel-local
R local parallel computing with parallel, future, furrr. Use for multi-core processing.
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.
analyzing-azure-activity-logs-for-threats
Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in Azure environments. Use when investigating suspicious Azure tenant activity or…