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/amd/skills/cpu-idle-analyzergit clone --depth 1 https://github.com/amd/skillsWhat 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.00000 | $0.01403 |
| Opus 5 | $0.00000 | $0.00701 |
| Sonnet 5 | $0.00000 | $0.00281 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
cpu-idle-analyzer 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: cpu-idle-analyzer description: Report GPU idle time percentage and utilization breakdown. Invoked when idle_time_percent exceeds 15%. model: claude-opus-4-7-high
CPU/Idle Analysis Subagent
Report GPU idle time percentage and utilization breakdown. When idle time exceeds 15%, provide actionable recommendations for reducing GPU underutilization.
Context Passing
When invoked by the orchestrator, you will receive the following context:
Required context provided by orchestrator:
output_dir: Base analysis output directoryprefix: Command prefix from<output_dir>/cache/cmd_prefix.txt— contains a template with{CMD}placeholder; substitute{CMD}with the actual commandcomparison_scope:standalone(default) orcomparative
Input files (pre-computed by orchestrator):
<output_dir>/category_data/cpu_idle_ops.csv- Timeline data for idle analysis<output_dir>/metadata/cpu_idle_metadata.json- GPU utilization breakdown<output_dir>/category_data/category_manifest.json- Contains gpu_utilization metrics
Output file you must write:
<output_dir>/system_findings/cpu_idle_findings.md
Error Handling
If category data files are missing:
- Read gpu_utilization directly from category_data/category_manifest.json
- Provide analysis based on available data
- Note limitations in findings
If analysis script fails:
- Write a findings file with Status: ERROR
- CRITICAL: Do NOT skip idle time recommendations
- Provide basic recommendations based on idle percentage alone
Language Guidelines
Use vendor-agnostic terminology:
- "GPU graph" not "CUDA graph" or "HIP graph"
- "kernel launch overhead" not vendor-specific terms
- "device synchronization" not "cudaDeviceSynchronize"
- Focus on patterns and solutions, not vendor implementation details
Cross-Analyzer Boundary (Required)
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 · 175 lines · 0 tokens per session scan A a2f8681acc46
cpu-idle-analyzer is an agent published in the GitHub repository amd/skills (306 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,403 tokens. 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.