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 skills add pantheon-org/tekhne --skill aws-console-navigatorgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/aws-console-navigator)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/aws-console-navigator"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/aws-console-navigator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pantheon-org/tekhne/aws-console-navigator"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/aws-console-navigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00094 | $0.01316 |
| Opus 5 | $0.00047 | $0.00658 |
| Sonnet 5 | $0.00019 | $0.00263 |
| Haiku 4.5 | $0.00009 | $0.00132 |
Grade A, and why
aws-console-navigator 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Console Navigator
Mindset
The CloudWatch console is a micro-frontend SPA embedded inside an iframe
(iframe[name="microConsole-Logs"]). This has three non-obvious consequences:
-
window.documentis the outer shell, not CloudWatch. All DOM queries must target the iframe'scontentDocument. In Playwright, usepage.frame({ name: 'microConsole-Logs' }). -
locator.click()on iframe elements times out. Playwright's locator API hits a 5 s timeout when clicking elements inside cross-origin iframes. Usepage.mouse.click(x, y)with coordinates calculated from the iframe bounding box + element'sgetBoundingClientRect. -
The results table is its own scroll container.
window.scrollBy()scrolls the outer shell. The CloudWatch results table lives inDIV.logs-table__wrapper. Scroll it directly:frame.evaluate(() => document.querySelector('.logs-table__wrapper').scrollTop = N).
When to Use This Skill
- Capturing AWS Console screenshots via Playwright MCP
- Authenticating via SSO and opening a specific account/role
- Getting step-by-step instructions to reach a CloudWatch Logs Insights query, alarm, or metric
- Guiding a user to navigate the console manually
When NOT to Use This Skill
- The target service does not use the microConsole iframe (e.g. S3, EC2) —
locator.click()works normally there - You only need to construct a CloudWatch URL without opening a browser — use
aws-cloudwatch-url-builderinstead
Navigating to CloudWatch Pages
Logs Insights
- Services → CloudWatch → Logs → Logs Insights
- Select the log group, paste the query, set the time range (Absolute), click Run query
Direct URL: See aws-cloudwatch-url-builder for the encoded URL template.
Alarms
- CloudWatch → Alarms → All alarms → search by alarm name → click alarm name
- Verify which metric is graphed before capturing screenshots
Direct URL:
https://{region}.console.aws.amazon.com/cloudwatch/home?region={region}#alarmsV2:alarm/{alarm_name}
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .audits/2026-04-06/analysis.md 1.3 KB
- .audits/2026-04-06/audit.json 530 B
- .audits/2026-04-06/remediation-plan.md 2.3 KB
- .audits/latest 10 B
- evals/scenario-01.md 2.3 KB
- evals/scenario-02.md 2.0 KB
- evals/scenario-03.md 2.6 KB
- references/console-reference.md 1.5 KB
- references/playwright-patterns.md 1.8 KB
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 · 143 lines · 94 tokens per session scan A 0db77c92325c
aws-console-navigator is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 1,316 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-09-03.
Other skills, from other repositories
linux-proxy
Install and configure Clash Meta / Mihomo proxy on Linux (Arch/fnOS/Debian) — Bettbox or mihomo-bin, subscription, DNS fix, LAN sharing, systemd, browser & FN-OS Chromium proxy, remote host config, dashboard panel. Use when user asks to set up proxy, share proxy with LAN, fix DNS hijack, or configure proxy on a…
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).