Borrowing it
Nothing to install: this file belongs to arsenyspb/comet-boundary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/arsenyspb/comet-boundary/main/.agents/skills/testing-comet-boundary/SKILL.mdgit clone --depth 1 https://github.com/arsenyspb/comet-boundaryWrote 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/arsenyspb/comet-boundary/testing-comet-boundary)<a href="https://agentmods.dev/skills/arsenyspb/comet-boundary/testing-comet-boundary"><img src="https://agentmods.dev/badge/skills/arsenyspb/comet-boundary/testing-comet-boundary.svg" alt="Measured on agentmods" height="20"></a>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.00037 | $0.01249 |
| Opus 5 | $0.00018 | $0.00624 |
| Sonnet 5 | $0.00007 | $0.00250 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
testing-comet-boundary scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST \ How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Comet Boundary
Prerequisites
- Docker and Docker Compose v2 must be available
- The Makefile uses
docker-compose(hyphenated) but newer systems only havedocker compose(space). Ifmake replayfails with "No such file or directory", usedocker composecommands directly.
Environment Setup
The project uses Docker Compose with these services:
postgres— Boundary databaseopenldap— LDAP directory for alice/bob userssetup— Database initialization (runs once)controller— Boundary controller (port 9200)worker— Boundary worker (port 9202)ssh-target-1,ssh-target-2— SSH targetsbackend— Go BFF (port 8080 internal)frontend— React/Vite app (port 5173)
Startup Sequence (if make replay doesn't work)
cd /path/to/comet-boundary
docker compose down -v
rm -f .env client/.env.local
docker compose up -d postgres openldap setup
docker wait comet-boundary-setup-1
docker compose up -d controller worker ssh-target-1 ssh-target-2
# Wait for controller to be healthy
bash scripts/01_setup-boundary.sh
docker compose up -d --build backend frontend
Verify All Services Healthy
docker compose ps # All should show "healthy" or "Up"
Test Credentials
- Boundary Admin: username
admin, password from setup script output (look for "Discovered Admin Password: ...") - LDAP Users:
alice / changeme(Team A),bob / changeme(Team B) - SSH credential (brokered): username
boundary-user, passwordpassword— stored in Boundary's Static Credential Store
Key Test Scenarios
1. Credential Store Verification (Boundary Admin UI, port 9200)
- Log in as admin at
http://localhost:9200 - Navigate: Generated org scope → Generated project scope → Credential Stores
- Verify "SSH Credential Store" exists (type: Static)
- Click into it → Credentials tab → verify "SSH Target Credential" exists (type: Username & Password)
- Navigate to Targets → "A Team Host" → Brokered Credentials tab → verify credential is linked
- Same for "B Team Host"
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.
- 8d ago First seen · 117 lines · 37 tokens per session scan A 0b55061d640a
testing-comet-boundary is a skill published in the GitHub repository arsenyspb/comet-boundary (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,249 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…