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 agentmods add skills/axisrow/claude_code_gmail_plugin/manage-labelsnpx skills add axisrow/claude_code_gmail_plugin --skill manage-labelsgit clone --depth 1 https://github.com/axisrow/claude_code_gmail_pluginWhat 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 | $0.00038 | $0.00397 |
| Opus 5 | $0.00019 | $0.00198 |
| Sonnet 5 | $0.00008 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
manage-labels 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 2d 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.
What it actually says
Manage Gmail Labels
List, create, and delete Gmail labels.
Arguments
$ARGUMENTS — subcommand: list (default), create <name>, or delete <label_id>.
Subcommand: list (default)
Use the Gmail MCP tool gmail_list_labels to get all labels.
Display in two sections:
System labels with localized names:
- INBOX → Входящие / Inbox
- SENT → Отправленные / Sent
- DRAFT → Черновики / Drafts
- TRASH → Корзина / Trash
- SPAM → Спам / Spam
- STARRED → Помеченные / Starred
- IMPORTANT → Важные / Important
- CATEGORY_PERSONAL → Личные / Personal
- CATEGORY_SOCIAL → Соцсети / Social
- CATEGORY_PROMOTIONS → Промоакции / Promotions
- CATEGORY_UPDATES → Обновления / Updates
- CATEGORY_FORUMS → Форумы / Forums
User labels — show name and ID (needed for tagging operations).
Subcommand: create
Run:
python3 ~/.claude/scripts/gmail-analyzer/create_label.py "<name>"
Report the created label's name and ID.
Subcommand: delete <label_id>
IMPORTANT: Ask user for confirmation before deleting. Show the label name and ID.
After confirmation, run:
python3 ~/.claude/scripts/gmail-analyzer/delete_label.py "<label_id>"
Respond in the user's language.
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.
- 2d ago First seen · 57 lines · 38 tokens per session scan A d1864cabc153
manage-labels is a skill published in the GitHub repository axisrow/claude_code_gmail_plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 397 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…