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 run-llama/vibe-llama --skill llamactlgit clone --depth 1 https://github.com/run-llama/vibe-llamaWrote 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/run-llama/vibe-llama/llamactl)<a href="https://agentmods.dev/skills/run-llama/vibe-llama/llamactl"><img src="https://agentmods.dev/badge/skills/run-llama/vibe-llama/llamactl/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/run-llama/vibe-llama/llamactl"><img src="https://agentmods.dev/badge/skills/run-llama/vibe-llama/llamactl.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.00051 | $0.00575 |
| Opus 5 | $0.00026 | $0.00287 |
| Sonnet 5 | $0.00010 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
Use llamactl - a CLI tool for LlamaAgents 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 11d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use llamactl - a CLI tool for LlamaAgents
llamactl is a CLI tool for developing and deploying LlamaIndex workflows as LlamaAgents. It provides commands to initialize projects, run local development servers, and manage cloud deployments.
Prerequisites
Before using llamactl, ensure you have:
uv- Python package manager and build tool- Node.js - Required for UI development (supports
npm,pnpm, oryarn) llama-index-workflowsandllamactlinstalled in your environment
Installation
Install llamactl globally using uv:
uv tool install -U llamactl
llamactl --help
Or try it without installing:
uvx llamactl --help
Initialize a Project
Create a new LlamaAgents project with starter templates:
llamactl init
This creates a Python module with LlamaIndex workflows and an optional UI frontend. Configuration is managed in pyproject.toml, where you define workflow instances, environment settings, and UI build options.
Local Development
Start the local development server:
llamactl serve
This command:
- Installs dependencies
- Serves workflows as an API (configured in
pyproject.toml) - Starts the frontend development server
The server automatically detects file changes and can resume in-progress workflows.
Deploy to LlamaCloud
Push your code to a git repository:
git remote add origin https://github.com/org/repo
git add -A
git commit -m 'Set up new app'
git push -u origin main
Create a cloud deployment:
llamactl deployments create
This opens an interactive Terminal UI to configure:
- Deployment name
- Git repository (supports private GitHub repos via the LlamaDeploy GitHub app)
- Git branch/tag/commit
- Environment secrets
Manage Deployments
- View deployment status:
llamactl deployments get - Update secrets or branch:
llamactl deployments edit - Deploy new version:
llamactl deployments update
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.
- 11d ago First seen · 90 lines · 51 tokens per session scan A 4b03210cdba1
Use llamactl - a CLI tool for LlamaAgents is a skill published in the GitHub repository run-llama/vibe-llama (178 stars, last pushed 10mo ago), licensed MIT. It adds 51 tokens to every session and 575 once invoked, about $0.0003 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…