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 vigilante-issue-implementation-on-dockergit 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/vigilante-issue-implementation-on-docker)<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-docker"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-docker/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/vigilante-issue-implementation-on-docker"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-docker.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.00870 |
| Opus 5 | $0.00023 | $0.00435 |
| Sonnet 5 | $0.00009 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade B, and why
vigilante-issue-implementation-on-docker scanned grade B 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 10d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Package management**: minimize installed packages and remove package manager caches in the same `RUN` layer (e.g., `apt-get install -y --no-install-recommends ... && rm -rf /var/lib/apt/lists/*`). Do not install debu Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vigilante Docker Issue Implementation
Focus
- Read the prompt for detected tech stacks, process hints, and Docker security guidance before changing code.
- Follow current Dockerfile best practices for image minimization, build efficiency, and secret-safe builds.
- Keep changes scoped to the issue and do not broaden into unrelated infrastructure redesign.
Dockerfile Best Practices
- Base images: pin base images to specific versions or digests rather than mutable tags like
latest. Prefer minimal base images (Alpine, distroless, scratch) to reduce attack surface. When the repository already uses digest-pinned or distroless images, preserve that convention. - Build structure: use multi-stage builds to separate build dependencies from the final runtime image. Set an explicit
WORKDIRrather than relying on the default. Combine relatedRUNcommands to minimize layers. Order instructions from least to most frequently changing to maximize build cache efficiency. Copy dependency manifests and install dependencies before copying application source. - Package management: minimize installed packages and remove package manager caches in the same
RUNlayer (e.g.,apt-get install -y --no-install-recommends ... && rm -rf /var/lib/apt/lists/*). Do not install debug tools, editors, or shells in production images unless the repository explicitly requires them. .dockerignore: ensure.dockerignoreexcludes build artifacts, test fixtures, secrets, and version-control metadata that should not enter the build context.
Secret-Safe Builds
- Never pass secrets through
ARGorENVinstructions — they persist in image history and layer metadata. - Use BuildKit secret mounts (
--mount=type=secret) for build-time secrets when the build requires credentials. - Do not copy secret files (
.env, credentials, tokens, private keys) into the image. - Ensure
.dockerignoreexcludes sensitive files and directories.
Runtime Security
- Run containers as a non-root user when practical — add a
USERinstruction after installing packages. - Prefer read-only root filesystems where the application supports it.
- Expose only the ports the application requires.
- Do not use
--privilegedor add unnecessary Linux capabilities unless the issue specifically requires it.
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.
- 10d ago First seen · 48 lines · 46 tokens per session scan B 776e71964462
vigilante-issue-implementation-on-docker is a skill published in the GitHub repository aliengiraffe/vigilante (40 stars, last pushed 2d ago), licensed Apache-2.0. It adds 46 tokens to every session and 870 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
skill-packager
Authors Agent Skills v1.0 packages (SKILL.md plus references/scripts), runs packageskill to produce a standards-compliant zip, and uses installskill to add skills from HTTPS, registry, workspace, or an uploaded archive. Use when the user wants to turn documentation, workflows, or code into a portable skill, export a…
workflow-helper
Guidance for creating, managing and executing workflow automations that chain multiple tools and agents together. Use when the user asks about building, listing, running or composing workflows and automated task pipelines.
data-analyzer
Guidance for analyzing structured data, generating statistics and producing data-driven insights. Use when the user asks to analyze data, compute statistics, find patterns, or generate analytical reports.
document-processor
Guidance for processing documents, extracting content, and transforming structured information. Use when the user asks to process, parse, extract, or transform document content such as PDFs, Word files, or spreadsheets.
attendance-signin-sheet
A spreadsheet generator for printable attendance or meeting sign-in sheets. It turns a list of names into rows with columns such as signatures, dates, departments, or employee IDs.
travel-expense-audit
A travel-expense review workflow that checks reimbursement claims against policy handbooks and rate tables. It covers items such as hotel, transport, and daily meal allowances.