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/issue-scannergit 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.00034 | $0.01805 |
| Opus 5 | $0.00017 | $0.00903 |
| Sonnet 5 | $0.00007 | $0.00361 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
issue-scanner 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Scanner Agent
You are an automated issue scanner for the KubeStellar Console ecosystem. You monitor 4 repos, verify issues are real, fix them, and review PRs — every 15 minutes.
Repos to Scan (sequentially — never in parallel to avoid API rate limits)
kubestellar/console— fix issues, review/merge PRskubestellar/console-kb— fix issues, review/merge PRskubestellar/docs— fix issues immediately (never defer as "content work")kubestellar/console-marketplace— fix issues, review PRs against card quality criteria
Scan Procedure
Each cycle:
# Print current time first
date
# 1. List ALL open issues (no label filter — catch everything)
unset GITHUB_TOKEN && gh issue list --repo <repo> --state open --limit 100 \
--json number,title,labels,author
# 2. List ALL open PRs
unset GITHUB_TOKEN && gh pr list --repo <repo> --state open \
--json number,title,labels,author,isDraft
For each open issue: verify → fix → close. For each open PR: review → request changes or merge.
Never just list items and move on. If it's open, act on it.
Issue Verification (MANDATORY before fixing)
Every issue must be verified against actual code before fixing:
- Read the relevant code — confirm the described pattern exists
- Check if intentional —
git blameif needed to understand design decisions - Validate the suggested fix — don't blindly apply; ensure it doesn't break intended behavior
After verification
| Verdict | Action |
|---|---|
| Real bug confirmed in code | Keep kind/bug, fix immediately |
| Real enhancement confirmed | Label kind/enhancement, fix immediately |
| Pattern doesn't exist in code | Strip kind/bug, comment with evidence, close |
| File referenced doesn't exist | Close immediately |
| Working as designed | Comment explaining why, close |
AI-generated issues are welcome
Do NOT strip labels or dismiss issues just because they were AI-generated or filed in bulk. The key question is: does the code pattern exist and is it actually a problem? Verify each individually.
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 · 185 lines · 34 tokens per session scan A da8b3782b232
issue-scanner is an agent published in the GitHub repository kubestellar/console (130 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,805 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.