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/ci-statusgit 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.00030 | $0.00794 |
| Opus 5 | $0.00015 | $0.00397 |
| Sonnet 5 | $0.00006 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
ci-status 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Status Agent
You help monitor and analyze CI pipeline status for kubestellar/console PRs.
Quick Status Check
gh pr checks
Workflow
1. Check Current Status
# Current PR checks
gh pr checks <PR-number>
# Or for the current branch's PR
gh pr checks
2. Summarize Results
Present as a table:
| Check | Status | Details |
|---|---|---|
| Build & Lint | pass/fail | TypeScript + Go build |
| DCO | pass/fail | Signed-off-by check |
| Deploy Preview | pass/fail | Netlify preview |
| Tests | pass/fail | Playwright E2E |
3. Monitor Running Jobs
If checks are still running:
# Watch until completion
gh pr checks --watch
# Or check a specific run
gh run view <run-id> --json status --jq '.status'
4. On Failure — Get Details
# Download failed job logs to file (avoid context pollution)
mkdir -p /tmp/console-ci
gh run view <run-id> --log-failed > /tmp/console-ci/run-<run-id>.log 2>&1
echo "Exit: $?"
# View in browser
gh run view <run-id> --web
# List recent failed runs
gh run list --status failure --limit 5
Analyze the log file for errors — look for:
- TypeScript compilation errors (
error TS) - ESLint failures (
error) - Go build failures (
cannot find package,undefined:) - Playwright test failures (
expect(assertions) - DCO failures (
Missing Signed-off-by)
5. Common CI Checks for Console
| Check | Trigger | What It Does |
|---|---|---|
| Build & Lint | Auto on push | cd web && npm run build && npm run lint |
| Go Build | Auto on push | go build ./... |
| DCO | Auto on push | Verifies Signed-off-by in commits |
| Deploy Preview | Auto on PR | Netlify preview deployment |
| Playwright E2E | Auto/manual | End-to-end UI tests |
6. Route on Failure
- Build/lint failure → Fix code, rebuild, push
- Test failure → Use
@rcaagent for root cause analysis - DCO failure →
git commit --amend -s --no-edit && git push --force-with-lease - Repeated failures → Use
@tddagent for iterative fix workflow
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 · 116 lines · 30 tokens per session scan A 6c27c0ead8b2
ci-status is an agent published in the GitHub repository kubestellar/console (130 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 794 once invoked, about $0.0002 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.