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.
git clone --depth 1 https://github.com/specsnl/agent-specsWrote 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/plugins/specsnl/agent-specs/docker)<a href="https://agentmods.dev/plugins/specsnl/agent-specs/docker"><img src="https://agentmods.dev/badge/plugins/specsnl/agent-specs/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/plugins/specsnl/agent-specs/docker"><img src="https://agentmods.dev/badge/plugins/specsnl/agent-specs/docker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
docker 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.
What it actually says
{
"name": "docker",
"description": "A Specs Docker specific plugin",
"author": {
"name": "Specsnl Team",
"email": "[email protected]",
"url": "https://github.com/specsnl"
},
"repository": "specsnl/agent-specs",
"license": "MIT",
"keywords": ["docker", "container", "specs", "plugin"],
"commands": "./commands"
}
What it installs
The manifest is a name and a version. 1 skill, 2 commands travel with it, and installing the plugin installs all of them — 94 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 14 lines scan A bc8cdf1d4de3
docker is a plugin published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
cloudflare-sandbox
Cloudflare Sandboxes SDK for secure code execution in Linux containers at edge. Use for untrusted code, Python/Node.js scripts, AI code interpreters, git operations.
docker-containerization
Write production-grade Dockerfiles, docker-compose configurations, multi-stage builds, and container optimization. Activate on "Dockerfile", "docker", "docker-compose", "container", "multi-stage build", "docker image", "container optimization", "docker security". NOT for Kubernetes orchestration, cloud-specific…
odh-security
Supply-chain security alerting and OCI image CVE comparison.
portal-skills
Platform engineering and security skills: GitLab CI/CD + Helm chart generation for Kubernetes, data-driven pod rightsizing from Prometheus, a proactive secure-coding baseline, and a deep OWASP reference (Top 10:2025, LLM Top 10, Agentic AI).
kubernetes-security
Kubernetes security: cluster hardening, RBAC audits, Pod Security Standards, NetworkPolicy, and admission control with Gatekeeper or Kyverno.
security-hardening
System hardening and CIS Benchmark assessment for Linux and Windows hosts, containers, Kubernetes, web servers, databases, and cloud accounts, with implementation and verification steps.