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 DDS-Solutions/AI-TadPole-OS --skill deployment-proceduresgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/deployment-procedures)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/deployment-procedures"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/deployment-procedures/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/dds-solutions/ai-tadpole-os/deployment-procedures"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/deployment-procedures.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01157 |
| Opus 5.5 | $0.00012 | $0.00463 |
| Sonnet 5.5 | $0.00006 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
deployment-procedures 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 6d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / deployment-procedures
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Unverified production rollout, failed rollback sequence, unbacked-up state loss, database migration divergence.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Production Deployment & State Transition Protocol
Core Philosophy: Never deploy unverified code. Always have an immediate, tested rollback path and a verified pre-migration state snapshot. Workflow Binding: Used directly during the
/deployworkflow.
📚 Progressive Disclosure & L3 Reference Index
Read REQUIRED deployment gates below; consult deep L3 Reference Guides on demand:
| L3 Resource | Scope & Purpose | Trigger / When to Load |
|---|---|---|
rollback_and_verification_matrix.md |
Platform runbooks (Docker/PM2/K8s), migration expand-and-contract, SQLite snapshot SOP | Staging-to-production transitions & emergency rollbacks |
deployment_validator.py |
Deterministic pre-flight deployment validator & health probe tool | Pre-flight git, migration, and health verification |
/deploy Workflow |
Sovereign state transition pipeline | Formal release management and audit gates |
🚀 1. The 5-Phase Release Pipeline
1. PREPARE ➔ Run parity_guard.py, test suites, and deployment_validator.py; verify clean git tree.
2. SNAPSHOT ➔ Force SQLite WAL checkpoint and create atomic database backup.
3. RELEASE ➔ Execute binary update or container rollout with real-time log monitoring.
4. VERIFY ➔ Probe /health endpoint; inspect latency and initial request telemetry.
5. CONFIRM ➔ If error rate > 0.1% or panic detected ➔ ROLLBACK IMMEDIATELY.
What ships with it
2 files 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.
- 6d ago Changed · +35 lines 654625a58fb0
- 1mo ago First seen · 61 lines · 29 tokens per session scan A c59d6413ccdd
deployment-procedures is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,157 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-31.
Other skills, from other repositories
deployment-rules
Release/deployment standards — semantic-release, commitlint, version sync, the updater. Load for /prepare-release and changes to release.config.mjs / commitlint / workflows / version files. Owned by project-steward.
github
A guide to using GitHub CLI, a command-line tool for working with GitHub repositories. It covers issues, pull requests, releases, labels, milestones, and workflow runs.
release-workflow
Release/publish the spikard Rust core crate and CLI end-to-end. Load when releasing or publishing spikard — cutting a new version, tagging, running gh release create, and installing the released build locally. Covers version set via Taskfile, CHANGELOG roll, the clean-tree precondition, GitHub release, local install…
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
create-pr
Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.