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.
git 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/plugins/vincentchuwaichow/vanguard-frontier-agentic/context-burn)<a href="https://agentmods.dev/plugins/vincentchuwaichow/vanguard-frontier-agentic/context-burn"><img src="https://agentmods.dev/badge/plugins/vincentchuwaichow/vanguard-frontier-agentic/context-burn/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/plugins/vincentchuwaichow/vanguard-frontier-agentic/context-burn"><img src="https://agentmods.dev/badge/plugins/vincentchuwaichow/vanguard-frontier-agentic/context-burn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context-burn 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 today.
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.
What it actually says
{
"name": "context-burn",
"version": "1.0.0",
"description": "Tracks context use per session in a status file and warns at 70% and 90% where the harness reports token use."
}
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.
- today First seen · 6 lines scan A 3bc75105bea3
context-burn is a plugin published in the GitHub repository VincentChuWaiChow/vanguard-frontier-agentic (24 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-17.
Other plugins, from other repositories
craft-statusline
A carefully crafted Claude Code statusline written in bash. Shows model, effort level, git branch (state-aware color palette), context window with absolute-token traffic light, rate limits, and optional cost.
agentcall
Let your AI agent join Google Meet, Zoom, or Microsoft Teams as a speaking, listening, presenting participant — works with Claude Code, Codex, Gemini CLI, and 30+ other agents.
codex-council
Independent cross-model verification and collaboration for Claude Code: Claude briefs task-specific OpenAI Codex roles with decision-complete context, routes each role to a runtime-discovered model and reasoning effort or your native Codex configuration, checks their evidence, and reconciles the findings into one…
claude-bedrock
Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.