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/cyaranpx skills add GoogleCloudPlatform/cxas-scrapi --skill cyaragit 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/cyara)<a href="https://agentmods.dev/skills/googlecloudplatform/cxas-scrapi/cyara"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/cxas-scrapi/cyara.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.00020 | $0.00451 |
| Opus 5 | $0.00010 | $0.00226 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
cxas-cyara-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 5d 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
Cyara Ingestor Skill
Use this skill when you need to extract dialogue turns and conversation flows from Cyara XML test case files.
Protocol
Cyara files are XML documents containing test scenarios for voice or chat agents. They are rich sources for transcripts because they map user utterances to agent states.
- Identify Test Cases: Look for elements representing individual test cases using their unique identifiers.
- Extract Utterances: Extract the list of sample user utterances. These are valuable for generating realistic User turns.
- Parse Expected Flow: Locate the
expected_flowsequence, which describes the chronological steps of the interaction. - Map Turns:
- Iterate through the
expected_flow. - Look for steps that include
(User: ...)annotations. This directly maps what the user said at that specific point in the flow. - The step names (e.g.,
Greeting_State,Ask_Identifier) indicate the Agent's state or prompt. You must infer natural Agent dialogue based on these state names if literal text is not provided.
- Iterate through the
- Voice-Realism Enforcement: Ensure the inferred dialogue strictly
enforces the main skill's Agent-First, Voice Realism (No Spoken
URLs), and Standardized End Session (closing with
end_sessiontool call) rules. - Extract Metadata: Look for intent tags to understand the high-level classification.
Example
A summarized Cyara item might look like this: `yaml id: test_case_identifier utterances:
- I need help with my account expected_flow:
- Welcome_Prompt (User: I need help with my account) - Request_Account_ID`
You should infer a transcript like:
- User: "I need help with my account."
- Agent: [Triggers Welcome Prompt and recognizes intent, proceeding to Request Account ID]
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.
- 5d ago First seen · 50 lines · 20 tokens per session scan A 4ea3c563fe15
cxas-cyara-ingestor is a skill published in the GitHub repository GoogleCloudPlatform/cxas-scrapi (95 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 451 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…