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 AlanHuang168/AI-Project-Workflow --skill deploygit clone --depth 1 https://github.com/AlanHuang168/AI-Project-WorkflowWrote 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/alanhuang168/ai-project-workflow/deploy)<a href="https://agentmods.dev/skills/alanhuang168/ai-project-workflow/deploy"><img src="https://agentmods.dev/badge/skills/alanhuang168/ai-project-workflow/deploy/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/alanhuang168/ai-project-workflow/deploy"><img src="https://agentmods.dev/badge/skills/alanhuang168/ai-project-workflow/deploy.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.00000 | $0.00579 |
| Opus 5.5 | $0.00000 | $0.00232 |
| Sonnet 5.5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
deploy 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: deploy description: Prepare deployment instructions, release checks, verification, monitoring, and rollback. Use when the project is ready for deployment or when the user invokes /deploy. version: 1.0.0 stage: deploy
Goal
Produce a deployment guide that can be executed and verified for the target environment.
Use Cases
- The user invokes
/deploy. - Review is complete and the project needs release instructions.
- The user asks for deployment, release, rollback, or operational verification guidance.
Preconditions
reviewis complete, or the user explicitly approves skipping review and records the reason.- Build and runtime requirements are known.
Required Context
AGENTS.md.ai-workflow/state.jsoncore/templates/DEPLOY.template.mddocs/PRD.mddocs/ARCH.mddocs/SDD.mddocs/TEST.mddocs/REVIEW.md- Relevant build, configuration, and deployment files
Inputs
- Target environment.
- Build and runtime constraints.
- User-provided deployment requirements.
Allowed Changes
docs/DEPLOY.md- Necessary deployment configuration when explicitly within scope
.ai-workflow/state.json
Steps
- Read review results, architecture, build files, and deployment constraints.
- Identify environment requirements, configuration, secrets handling, build steps, deployment steps, verification, monitoring, and rollback.
- Do not invent credentials or claim access to systems that were not verified.
- Write
docs/DEPLOY.md. - Run available deployment-related validation if it is safe and in scope.
- Update workflow state:
documents.deploy = "complete", adddeploytocompletedStages, setcurrentStage = "retro", and update the timestamp.
Outputs
docs/DEPLOY.md- Updated
.ai-workflow/state.json
Acceptance Criteria
- DEPLOY includes environment requirements, configuration, build, deployment, migration, verification, monitoring, rollback, and release checklist.
- Secrets are not written into the repository.
- Verification results are reported honestly.
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 · 84 lines · 0 tokens per session scan A 375f2898ec0f
deploy is a skill published in the GitHub repository AlanHuang168/AI-Project-Workflow (29 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 579 tokens. 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
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
best-practices
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
code-documentation
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.