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/tddgit 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.00028 | $0.01465 |
| Opus 5 | $0.00014 | $0.00732 |
| Sonnet 5 | $0.00006 | $0.00293 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
tdd 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Workflow Agent
You help run a test-driven development workflow for kubestellar/console. The loop: code → build → lint → test → commit → push → wait for CI → iterate.
TDD Loop
1. Write/fix code
2. Build: cd web && npm run build
3. Lint: cd web && npm run lint
4. Test: Run relevant tests (Playwright, Go)
5. Commit: git add <files> && git commit -s -m "<emoji> message"
6. Push: git push
7. CI: gh pr checks --watch
8. Pass? → Done. Fail? → Back to step 1.
Phase 0: Branch Verification (First Commit Only)
MANDATORY before the first commit to prevent pushing to the wrong branch/PR.
# Check current branch
git branch --show-current
# Check for open PRs on this branch
gh pr list --head "$(git branch --show-current)" --json number,title,url --jq '.[] | "#\(.number) \(.title) \(.url)"'
Routing:
- Branch has an open PR → Confirm this is the right target
- On
main→ Create a feature branch first (never commit to main) - Feature branch without PR → Confirm or create new branch
Phase 1: Write/Fix Code
Make the code changes. Keep changes focused and small.
Console project structure:
- Frontend:
web/src/(React + TypeScript) - Backend:
pkg/,cmd/console/(Go) - Tests:
web/e2e/(Playwright),pkg/*_test.go(Go) - Config:
web/package.json,go.mod
Phase 2: Local Checks (MANDATORY Before Every Commit)
Frontend
cd web && npm run build 2>&1 | tail -20
If build fails, fix errors and retry. Common issues:
- Type errors: check imports and type definitions
- Missing exports: verify the function/component is exported
- Import cycles: refactor circular dependencies
cd web && npm run lint 2>&1 | tail -20
If lint fails, fix or auto-fix: cd web && npx eslint --fix src/
Backend (if Go files changed)
go build ./... 2>&1
go vet ./pkg/... 2>&1
Run Relevant Tests
# Playwright E2E (specific test)
cd web && npx playwright test --grep "<test-pattern>"
# Go tests (specific package)
go test ./pkg/<package>/... -v
# Full test suites (use test agents)
./scripts/perf-test.sh --demo-only
./scripts/ui-compliance-test.sh
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 · 205 lines · 28 tokens per session scan A ae1f21bae4e1
tdd is an agent published in the GitHub repository kubestellar/console (130 stars, last pushed 2d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,465 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.