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 EntityProcess/agentv --skill deploy-plangit clone --depth 1 https://github.com/EntityProcess/agentvWrote 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/entityprocess/agentv/deploy-plan)<a href="https://agentmods.dev/skills/entityprocess/agentv/deploy-plan"><img src="https://agentmods.dev/badge/skills/entityprocess/agentv/deploy-plan/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/entityprocess/agentv/deploy-plan"><img src="https://agentmods.dev/badge/skills/entityprocess/agentv/deploy-plan.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.00037 | $0.00252 |
| Opus 5.5 | $0.00015 | $0.00101 |
| Sonnet 5.5 | $0.00007 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
deploy-plan 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
Deploy Plan Skill
Purpose
Create a structured deployment plan from a release specification. Produces {output_dir}/deploy-plan.md with step-by-step instructions, dependency ordering, and rollback checkpoints.
When to Use
- Planning a new deployment from a release spec
- Coordinating multi-service deployments with dependency ordering
- Generating rollback checkpoints for each deployment step
Process
- Read the release specification
- Identify affected services and their dependencies
- Order deployments by dependency graph (databases first, then backends, then frontends)
- For each service, define: pre-deploy checks, deploy command, health check, rollback command
- Write
{output_dir}/deploy-plan.md
Phase Handoff
After completing the plan, tell the user:
"Next step — run: /deploy-execute {output_dir} Or let the orchestrator continue automatically."
Skill Resources
references/deployment-patterns.md— Common deployment patterns and anti-patterns
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.
- 1mo ago First seen · 39 lines · 37 tokens per session scan A 722a294dd597
deploy-plan is a skill published in the GitHub repository EntityProcess/agentv (15 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 252 once invoked, about $0.0001 per session on Opus 5.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
neuron-laravel-integration
Integrate Neuron AI agents into a Laravel 13 app the framework-native way — setup checklist (App\Neuron layout, config/services.php keys, one migration, NeuronServiceProvider, bootstrap/app.php exception mapping, neuron:evaluate), container-built agents bound per thread with for(), thread authorization, JSON and…
neuron-symfony-integration
Integrate Neuron AI agents into a Symfony 8 app, from packages, env keys, a Doctrine migration for the Neuron tables and services.yaml wiring to a shared agent bound per request with for(), a thread voter, JSON and AG-UI (CopilotKit) or useChat streaming with StreamedResponse, reload with pending approvals, Messenger…
neuron-evaluation
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
neuron-workflow
Build or modify Neuron AI Workflow graphs, including nodes, events, middleware, persistence, parallel branches, streaming, and human-in-the-loop interruption. Use for tasks specifically involving Neuron's Workflow APIs or custom Neuron agentic orchestration; do not trigger for generic workflow or event-driven design…
neuron-agent
Create, configure, and extend Neuron AI agents in PHP using providers, tools, chat history, memory, and custom workflow nodes. Use for Neuron Agent implementation, configuration, conversation lifecycle, and input/output extensions.
neuron-streaming
Stream Neuron AI agent and workflow output to a consumer — iterating native chunks, yielding portable progress events from nodes, attaching a stream adapter for a UI protocol (Vercel AI SDK, AG-UI, SSE) or for Neuron's native vocabulary, and pushing output through a streaming channel when the consumer is not the HTTP…