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.00152 | $0.02441 |
| Opus 5.5 | $0.00061 | $0.00976 |
| Sonnet 5.5 | $0.00030 | $0.00488 |
| Haiku 4.5 | $0.00015 | $0.00244 |
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 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Delegation
The orchestrator's context window is the scarcest resource in a session. Every file dump, log tail, and grep result read directly is context that can no longer hold the plan, the spec, or the diff under review. Delegation exists to keep that window for judgment.
Opus 5.5 is the daily driver: it is the orchestrator, and it makes the code edits. Reading work goes to cheaper models.
Route each step by the kind of work
| Work | Who does it | Model | Effort |
|---|---|---|---|
| Search, recon, mapping call sites, "where does X live" | subagent (Explore) |
haiku; sonnet when interpreting what it finds takes judgment |
none on Haiku |
| Reading CI or gate logs, running the gate suite | subagent | haiku or sonnet |
none on Haiku |
| Bulk prose: docs pages, guides, templates, against an exact spec | subagent | sonnet |
session level |
| Code edits: scripts, tests, generators, gates, workflow code, Rust | orchestrator, or opus subagents for independent parallel edits |
Opus 5.5 | session level |
| Architecture, schema shapes, security-sensitive and load-bearing edits | orchestrator only | Opus 5.5 | session level |
| Verification of delegate output, and the commit | orchestrator only | Opus 5.5 | session level |
One task that high has failed twice in the same way |
orchestrator, after switching model | Fable 5.1 | then switch back |
Search and log-reading are summarization jobs: a cheaper model reads a lot and returns a little, and that is exactly the trade you want. Code edits are the opposite. They are where a subtle mistake costs a CI cycle and a reviewer's trust, and a spec rarely captures every invariant the surrounding code depends on. Keep them on the model that holds the whole plan.
Docs prose is the judgment call in this table. It is not code, so a Sonnet writer with an exact file-scoped spec is still the default. Anything that encodes facts (model names, command flags, API shapes) gets verified by the orchestrator before acceptance, whoever wrote it.
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 Changed · +45 lines · +92 tokens per session a48b0f6c472f
- 1mo 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 (24 stars, last pushed yesterday), licensed Apache-2.0. It adds 152 tokens to every session and 2,441 once invoked, about $0.0006 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-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.
r-parallel-local
R local parallel computing with parallel, future, furrr. Use for multi-core processing.
limma
R limma package for microarray and RNA-seq. Use for linear models in differential expression.
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…