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/googlecloudplatform/cxas-scrapi/drawionpx skills add GoogleCloudPlatform/cxas-scrapi --skill drawiogit clone --depth 1 https://github.com/GoogleCloudPlatform/cxas-scrapiWrote 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/googlecloudplatform/cxas-scrapi/drawio)<a href="https://agentmods.dev/skills/googlecloudplatform/cxas-scrapi/drawio"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/cxas-scrapi/drawio.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00019 | $0.01217 |
| Opus 5 | $0.00010 | $0.00609 |
| Sonnet 5 | $0.00004 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
cxas-drawio-ingestor 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 4d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draw.io Ingestor Skill
Use this skill when you need to extract dialogue turns and conversation flows
from .drawio diagram files.
Protocol for Flowchart & Diagram Traversal
When processing .drawio flowchart designs, you must parse them as complete
directed graphs to construct dialogue paths, rather than extracting flat text
turns.
1. Parse Graph Structural Topology
- Scan
<mxCell>tags wherevertex="1". Extract theiridandvalue(text label). - Scan
<mxCell>tags whereedge="1". Matchsourceandtargetvertex IDs to identify directed pathways. - Clean cell text by stripping internal HTML styling, tags, and formatting
metadata (e.g.,
<div>,<font>, CSS styles). Unescape HTML entities (e.g.,"or<) to obtain clean text.
2. Dialogue State & Path Traversal
- Locate the start node (typically a top-level cell labeled "Start", "Welcome", or "Entry").
- Perform a step-by-step traversal (DFS/BFS) along the directed edges. Each unique path from start to a terminal node constitutes a distinct conversation flow.
- State Mapping:
- Prompt Node: Maps to an Agent Turn (using the node's cleaned label).
- Directed Edge Label: Maps to a User Input (representing speech utterances or DTMF keys that trigger that transition).
- Computational Node: Maps to a System Action / Webhook (e.g., database lookups or validation calls).
- Decision Diamond: Represents logical branching.
3. Brand and Domain Consistency Mapping
Ensure that you map all domain concepts consistently to the target brand or theme requested by the user or specified in the requirements. Do not mix multiple industrial domains in a single report.
- If the target brand has specific concepts, map requirements to fit that brand's services.
- If no brand is specified, use clean, generic customer service phrasing suitable for the context.
- Avoid using technical or backend-specific terminology in spoken Agent turns.
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.
- 4d ago First seen · 121 lines · 19 tokens per session scan A 338f5ba03f7a
cxas-drawio-ingestor is a skill published in the GitHub repository GoogleCloudPlatform/cxas-scrapi (95 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 1,217 once invoked, about $0.0001 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
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…