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 commands/youngjaedev/my-claude-plugins/deploy-docgit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWhat 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.00026 | $0.00715 |
| Opus 5 | $0.00013 | $0.00358 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
deploy-doc 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Doc Command
Produce a consistent client-facing deployment / procedure document (.md): a top-of-file summary, a prerequisites checklist, and numbered procedure steps. The enforceable skeleton lives in the deploy-doc-guide skill (the cross-runtime SSOT); this command orchestrates Read/Write around it.
Arguments
generate- Author a new procedure doc from collected input.rewrite- Restructure an existing.mdinto the skeleton, preserving its content.
Options
--title TITLE- Document title, emitted as the# H1on the first line (above the untitled summary paragraph). If omitted, ask or infer from input.--lang ko|en- Output language. Defaultko.--links <doc1,doc2>- SSOT documents the procedure links to instead of redefining (detailed contracts / specs that must NOT be inlined).
Instructions
For generate
- Load the
deploy-doc-guideSkill — its## Quick Referenceis the binding skeleton + self-verify checklist. - Collect: title, a 2-3 line core summary, prerequisite items, and the ordered procedure steps.
- Emit the skeleton in this order:
# H1document title from--title(first line). Omit only when no title is given/inferable.- Untitled summary paragraph (2-3 lines, no section heading) directly below the title and above the first
##. ## 전제조건(or## Prerequisitesfor--lang en) — every item as a- [ ]checklist line.## 절차(or## Procedure) — each step as### 1./### 2./### N., contiguous numbering from 1.
- Number-match rule: the count of steps named/implied in the summary MUST equal the number of
### N.headings. - Link, don't redefine: detailed contracts and SSOT details go to the
--linksdocuments as links; never inline them.
For rewrite
- Read the target file.
- Map existing content onto the skeleton:
- Move redefined contracts/specs to links (demote inline contracts to
--linksreferences). - Renumber procedure prose into contiguous
### N.headings. - Lift or synthesize the 2-3 line summary to the top as an untitled paragraph.
- Move redefined contracts/specs to links (demote inline contracts to
- Preserve original prose verbatim where possible — this is a surgical restructure, not a rewrite of wording.
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.
- 2d ago First seen · 65 lines · 26 tokens per session scan A a55492edcf3b
deploy-doc is a command published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 715 once invoked, about $0.0001 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-31.
Other commands, from other repositories
compile_paper
Convert a SWARM paper from markdown to LaTeX (if needed), compile to PDF, and open it.
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
brand-generate
Generate an on-brand document from a saved Brand Profile.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
Draft SSP From Extraction
Draft a schema-valid OSCAL SSP from extracted legacy sections, optionally importing a real FedRAMP baseline profile.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].