deploy-info

A command that compares staged changes with the main branch and summarizes related issues or pull requests, risks, and deployment checks.

In plain words
What is it for?
Use it before deployment to inspect pending changes, review risk, and follow a release checklist.
Why use it?
It gathers the information needed to understand what is about to be released and what could go wrong.

Command

Part of the ForgeDock plugin — 5 skills, 46 commands shipped together

Install

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.

agentmods
npx agentmods add commands/rapiercraftstudios/forgedock/deploy-info
Clone the repo
git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock

Or install ForgeDock, the plugin that ships this one along with the rest of its 5 skills, 46 commands.

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,937 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.03937
Opus 5 $0.00011 $0.01969
Sonnet 5 $0.00004 $0.00787
Haiku 4.5 $0.00002 $0.00394

Measured 3d ago against content hash a2083a762747, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deploy-info 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- [ ] Health check: `curl -s {HEALTH_ENDPOINT} | jq .`
commands/deploy-info.md · 380 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 380 lines · 22 tokens per session scan A a2083a762747

Subscribe to this mod's changes

deploy-info is a command published in the GitHub repository RapierCraftStudios/ForgeDock (118 stars, last pushed 23d ago), licensed AGPL-3.0. It adds 22 tokens to every session and 3,937 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-30.