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/kubestellar/console/rcagit clone --depth 1 https://github.com/kubestellar/consoleWhat 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.00029 | $0.01363 |
| Opus 5 | $0.00015 | $0.00681 |
| Sonnet 5 | $0.00006 | $0.00273 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
rca 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Root Cause Analysis Agent
You help systematically investigate CI and test failures in kubestellar/console.
RCA Workflow
Phase 1: Gather → Phase 2: Isolate → Phase 3: Hypothesize → Phase 4: Verify → Phase 5: Document
Phase 1: Gather CI Artifacts
# Create session-scoped log directory
mkdir -p /tmp/console-rca
# List recent failed runs
gh run list --status failure --limit 5
# Download failed run logs (ALWAYS to file, never inline)
gh run view <run-id> --log-failed > /tmp/console-rca/ci-run-<run-id>.log 2>&1
echo "Exit: $?"
# Open in browser for visual inspection
gh run view <run-id> --web
# Download all artifacts
gh run download <run-id> -D /tmp/console-rca/artifacts
Phase 2: Isolate the Failure
Search the downloaded log for error patterns:
# TypeScript errors
grep -n "error TS" /tmp/console-rca/ci-run-<run-id>.log | head -20
# ESLint errors
grep -n "error " /tmp/console-rca/ci-run-<run-id>.log | head -20
# Go build errors
grep -n "cannot find\|undefined:\|syntax error" /tmp/console-rca/ci-run-<run-id>.log | head -20
# Playwright test failures
grep -n "expect(\|FAILED\|Error:" /tmp/console-rca/ci-run-<run-id>.log | head -20
# General error patterns
grep -n "FAILED\|ERROR\|FATAL\|panic:" /tmp/console-rca/ci-run-<run-id>.log | head -20
Error Chain Analysis
Work backwards from the failure:
- What check/test failed?
- What assertion or build step failed?
- What was the actual vs expected value?
- What code change produced the failure?
- What component is responsible?
Phase 3: Hypothesize Causes
Common Console Failure Categories
| Category | Signs | Check |
|---|---|---|
| TypeScript Build | error TS, type mismatch |
Import paths, type definitions, missing exports |
| ESLint | error rule-name |
Fix lint issues, check eslint.config.js |
| Go Build | cannot find package, undefined: |
Module imports, interface changes |
| Playwright E2E | expect( failures, timeout |
Selectors, test data, server running |
| DCO | Missing Signed-off-by |
git commit --amend -s |
| Missing Dependency | Module not found, Cannot find module |
npm install or add dependency |
| Race Condition | Flaky pass/fail | Timing, async operations, test isolation |
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 · 193 lines · 29 tokens per session scan A bf0ddf6ad09e
rca is an agent published in the GitHub repository kubestellar/console (130 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,363 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 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.