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/llaa33219/casabot/agentnpx skills add llaa33219/casabot --skill agentgit clone --depth 1 https://github.com/llaa33219/casabotWrote 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/llaa33219/casabot/agent)<a href="https://agentmods.dev/skills/llaa33219/casabot/agent"><img src="https://agentmods.dev/badge/skills/llaa33219/casabot/agent.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.00015 | $0.01988 |
| Opus 5 | $0.00008 | $0.00994 |
| Sonnet 5 | $0.00003 | $0.00398 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade D, and why
Agent Creation & Management scanned grade D with 2 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
# Check if sudo is available Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/casabot/workspaces/<agent-name> How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Creation & Management
This manual explains how the base agent creates and manages podman-based sub-agents.
1. Install podman
podman is needed before creating sub-agents.
Step 1: Check if podman is already installed
which podman && podman --version
If podman is found, skip to Section 2.
Step 2: Gather system information
Try to detect as much as possible automatically before involving the user.
# Detect distro
cat /etc/os-release
# Check if sudo is available
sudo -n true 2>/dev/null && echo "sudo: available" || echo "sudo: not available"
If auto-detection fails or sudo is unavailable, ask the user for clarification. You may also ask about preferences like rootless mode or custom storage locations if relevant.
Step 3: Install podman
# Debian / Ubuntu
sudo apt update && sudo apt install -y podman
# Fedora / RHEL / CentOS
sudo dnf install -y podman
# Arch Linux
sudo pacman -S podman
# openSUSE
sudo zypper install -y podman
If rootless mode is desired, configure subuid/subgid:
sudo usermod --add-subuids 100000-165535 --add-subgids 100000-165535 $(whoami)
podman system migrate
Step 4: Verify installation
podman --version
podman info
Consider using the memory skill to save the detected distro and podman version for future reference.
2. Configure podman storage
Check the path where container images and layers are stored, and verify sufficient disk space.
# Check storage path
podman info --format '{{.Store.GraphRoot}}'
# Check disk usage
df -h $(podman info --format '{{.Store.GraphRoot}}')
If space is insufficient, graphroot in ~/.config/containers/storage.conf can be adjusted.
3. Create sub-agent container
All sub-agent containers should be assigned the casabot label for identification.
# Create a new agent container
podman run -d \
--name <agent-name> \
--label casabot=true \
-v ~/casabot/workspaces/<agent-name>:/workspace \
-v ~/casabot/skills:/skills:ro \
node:20-slim sleep infinity
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.
- 4d ago First seen · 290 lines · 15 tokens per session scan D a97e9c711f41
Agent Creation & Management is a skill published in the GitHub repository llaa33219/casabot (5 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,988 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.