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 skills add aliengiraffe/vigilante --skill docker-compose-launchgit clone --depth 1 https://github.com/aliengiraffe/vigilanteWrote 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/aliengiraffe/vigilante/docker-compose-launch)<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/docker-compose-launch"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/docker-compose-launch/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/docker-compose-launch"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/docker-compose-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00501 |
| Opus 5.5 | $0.00010 | $0.00200 |
| Sonnet 5.5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
docker-compose-launch 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 1mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Compose Launch
Overview
Use this skill only when the selected implementation workflow explicitly needs local services before app startup, migrations, or tests can run. Keep all service startup scoped to the assigned worktree and treat Docker Compose as a reusable helper for local implementation and test dependencies only.
Invocation Contract
The parent implementation skill should pass or infer this contract before acting:
required:trueorfalseworktree_path: absolute path to the assigned worktreeservice_types: one or more ofmysql,mariadb,postgres, ormongodbreason: short explanation of which app, package, migration, or test command needs the servicespreferred_mechanism: repository-native compose file, repo script, or fallback compose generation
If required is false, return status: not_needed and do nothing else.
Execution Rules
- Prefer repository-owned
docker-compose.yml,docker-compose.yaml,compose.yml, orcompose.yamlfiles before generating new files. - Prefer repository scripts or task-runner commands that already wrap Compose when they are documented and usable.
- Namespace any generated project name, file, network, volume, or container identifiers to the assigned worktree.
- Wait for service readiness before reporting success.
- Surface the exact startup and teardown commands that were used.
Structured Result
Return a concise structured summary using these fields:
status:ready,not_needed, orfailedservices: services that were started or detectedmechanism:repo_compose,repo_script, orgenerated_fallbackcommands: startup, readiness, and teardown commandsconnection: host, port, database, username, URL, or env hints when availablecleanup: explicit stop command, ornoneartifacts: compose files or env files created or reusednotes: concise caveats or follow-up steps
Guardrails
- Do not launch services outside the assigned worktree scope.
- Do not assume every repository needs Docker Compose.
- Do not replace a documented repository-native startup flow with a generated one unless the native path is unusable.
- Do not claim success until the requested service is accepting connections.
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.
- 1mo ago First seen · 46 lines · 24 tokens per session scan A 4e89fae705e0
docker-compose-launch is a skill published in the GitHub repository aliengiraffe/vigilante (40 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 501 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the $rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…
using-rn-dev-agent
Entry point for the rn-dev-agent plugin. Maps user intent to the right command, agent, or skill. Use at the START of any React Native development conversation. Triggers on "I want to build", "build a feature", "add a feature to the app", "test this", "something is broken", "fix the crash", "help with my React Native…
creating-actions
This skill should be used when the user asks to "create an action", "save this flow as an action", "make this replayable", "record a reusable action", "author a Maestro flow as an action", "add a login/setup action", or when a verified UI walk should be persisted under .rn-agent/actions/ so future sessions can replay…