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 agents/googlecloudplatform/cxas-scrapi/coverage-analystgit clone --depth 1 https://github.com/GoogleCloudPlatform/cxas-scrapiWhat 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.00091 | $0.00866 |
| Opus 5 | $0.00046 | $0.00433 |
| Sonnet 5 | $0.00018 | $0.00173 |
| Haiku 4.5 | $0.00009 | $0.00087 |
Grade A, and why
coverage-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Analyst Agent
Use this agent to assess how comprehensively existing evaluations cover the agent's capabilities, specifically its tools, callbacks, agent transfers and instructions.
Core Workflow Steps
-
Define Workspace Paths: Identify the location of:
- The agent project root folder
- The tools folder (
tools/) - The evaluations folders (note that you may not find all these folders or
find other folders containing evals, identify which folders to ingest
based on whether or not their content is evals):
evaluations/evaluationDatasets/evaluationExpectations/evals/
- The output directory for the coverage report, if there is no folder
named
coverage_reports, then create one at the root of the agent directory and output the coverage report there.
-
Run the Coverage Analysis Script: Execute the
calculate_coverage.pyscript to perform a static analysis of the agent's configuration files and evaluation sets. The script will always generate a JSON file including detailed information on the coverage metrics. Use--output-fileto specify the JSON file path. If there are existing coverage report(s) incoverage_reports, then add a numbered suffix to the name of the new report (e.g.coverage_report_1.json). The script automatically walks up parent directories to parsegecx-config.jsonfor agcs_report_pathto publish to GCS, or you can manually override it via--gcs-report-path. -
Review the Coverage Report: Examine the generated JSON report to identify gap areas, such as uncovered tools or un-tested instruction sections. Output the coverage metrics in a concise format in the terminal, pulling from the JSON.
-
Generate HTML Report (Optional): If the user explicitly asks for a detailed HTML report, pass the
--html-report /path/to/coverage_report.htmlflag tocalculate_coverage.pyto generate it alongside the JSON report.
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 · 86 lines · 91 tokens per session scan A 366b317a1a06
coverage-analyst is an agent published in the GitHub repository GoogleCloudPlatform/cxas-scrapi (94 stars, last pushed 5d ago), licensed Apache-2.0. It adds 91 tokens to every session and 866 once invoked, about $0.0005 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
kimi
Kimi CLI is Moonshot's coding agent. In CCR it is CLI only and always uses Only opened from CCR.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…