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 skills/rajitsaha/100xprism/launchnpx skills add rajitsaha/100xprism --skill launchgit clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/launch)<a href="https://agentmods.dev/skills/rajitsaha/100xprism/launch"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/launch.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 | $0.00037 | $0.02971 |
| Opus 5 | $0.00018 | $0.01486 |
| Sonnet 5 | $0.00007 | $0.00594 |
| Haiku 4.5 | $0.00004 | $0.00297 |
Grade A, and why
launch 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 5d 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 http://localhost:8000/health 2>/dev/null || \ How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch — Pre-flight Pipeline: Docker → Test → Lint → Security → Build → Commit → Push → Cleanup
Release engineer mode: execute each phase in order; each must fully complete before advancing. Do NOT ask for permission. Stop only if something is truly unfixable.
Phase 0 — Docker Build & Smoke Test (if applicable)
PROJECT_ROOT=$(git rev-parse --show-toplevel)
ls "$PROJECT_ROOT/Dockerfile" 2>/dev/null && echo "HAS_DOCKERFILE" || echo "NO_DOCKERFILE"
Skip this phase if no Dockerfile exists. Otherwise:
0a. Build images
Detect multiple services from docker-compose.yml. Build all:
cd "$PROJECT_ROOT"
docker build -t $(basename $PROJECT_ROOT)-api:local . 2>&1
# If dashboard/frontend Dockerfile exists:
docker build -t $(basename $PROJECT_ROOT)-dashboard:local ./dashboard 2>&1 || true
Fix build errors; iterate until all images build.
0b. Start stack
# Use docker-compose.yml or compose.yml if present
COMPOSE_FILE=$(ls docker-compose.yml compose.yml deploy/docker-compose.yml 2>/dev/null | head -1)
[ -n "$COMPOSE_FILE" ] && docker compose -f "$COMPOSE_FILE" up -d || docker compose up -d
docker compose ps
Expected: all services running/healthy.
0c. Run migrations (if applicable)
docker compose run --rm migrate 2>/dev/null || true
0d. Smoke test
Read the project instruction file or README.md for the health endpoint; fall back to common defaults:
curl -s http://localhost:8000/health 2>/dev/null || \
curl -s http://localhost:3000/health 2>/dev/null || \
curl -s http://localhost:8080/health 2>/dev/null || echo "No health endpoint found"
0e. Cleanup
docker compose down 2>/dev/null || true
GATE: All images build, containers healthy, smoke test passes.
Phase 1 — Tests
Run the test workflow, which will:
- Auto-start required Docker services (DB, Redis, etc.) for integration tests
- Run unit tests against real services — no DB mocks
- Run integration tests against a real Docker DB
- Run E2E tests against the full docker compose stack
- Loop until all thresholds are met with zero failures
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 330 lines · 37 tokens per session scan A c5e4e6bd4dc9
launch is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 2,971 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
ios-appstore-builder
Prepare, configure, and publish iOS apps to the Apple App Store. Covers certificates, provisioning profiles, TestFlight, App Store submission, and review guidelines.
analytics-audit
Audit analytics implementations for tracking gaps and data quality issues.
app-release-manager
Manage the complete mobile app release lifecycle from versioning to store submission.
data-archiver
Professional Data Archiver Expert skill. Design and maintain secure, optimized, and performant databases and data storage solutions.
data-governance
Professional Data Governance Expert skill. Design and maintain secure, optimized, and performant databases and data storage solutions.
data-warehouse
Professional Data Warehouse Expert skill. Design and maintain secure, optimized, and performant databases and data storage solutions.