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 commands/enuno/dokploy/create-containergit clone --depth 1 https://github.com/enuno/dokployWhat 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.00013 | $0.01402 |
| Opus 5 | $0.00006 | $0.00701 |
| Sonnet 5 | $0.00003 | $0.00280 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
create-container 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 yesterday.
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.
allowed-tools: Read, Write, Bash(docker:*, curl:*, wget:*, git:*) How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build a Docker image from a Dockerfile (local or URL) and push it to the private registry at registry.hashgrid.net.
Step 1: Parse Arguments
Extract the Dockerfile path from the first argument. Check if a custom image tag was provided as the second argument.
Step 2: Validate Dockerfile Source
Determine if the Dockerfile path is:
- Local file: Check if it exists using the Read tool
- URL: Must start with
http://orhttps://
If URL, download it to a temporary location:
!curl -fsSL <dockerfile-url> -o /tmp/Dockerfile.tmp
Step 3: Generate Image Tag
If no custom tag provided, auto-generate one:
- Get current directory name:
!basename $(pwd) - Try to get git commit hash:
!git rev-parse --short HEAD 2>/dev/null || echo "latest" - Format:
<directory-name>:<git-hash>or<directory-name>:latest
If custom tag provided, use it directly.
Step 4: Check Registry Authentication
Verify login to registry.hashgrid.net:
!docker login registry.hashgrid.net --password-stdin < /dev/null 2>&1
If not authenticated, instruct user:
⚠️ Not logged into registry.hashgrid.net
Please run: docker login registry.hashgrid.net
Then stop execution.
Step 5: Build Docker Image
Build the image from the Dockerfile:
If local Dockerfile:
!docker build -f <dockerfile-path> -t <image-tag> <build-context-dir>
If downloaded from URL:
!docker build -f /tmp/Dockerfile.tmp -t <image-tag> .
The build context directory is the directory containing the Dockerfile (or current directory for URLs).
Show the build output to the user.
Step 6: Tag for Registry
Tag the image with the registry prefix:
!docker tag <image-tag> registry.hashgrid.net/<image-tag>
Step 7: Push to Registry
Push the tagged image:
!docker push registry.hashgrid.net/<image-tag>
Show push progress to the user.
Step 8: Cleanup and Report
If Dockerfile was downloaded from URL, remove it:
!rm -f /tmp/Dockerfile.tmp
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.
- yesterday First seen · 202 lines · 13 tokens per session scan A f493e01a2443
create-container is a command published in the GitHub repository enuno/dokploy (2 stars, last pushed 21d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,402 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.