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 infraspecdev/tesseract --skill deployment-safety-reviewgit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/deployment-safety-review)<a href="https://agentmods.dev/skills/infraspecdev/tesseract/deployment-safety-review"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/deployment-safety-review/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/infraspecdev/tesseract/deployment-safety-review"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/deployment-safety-review.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.00062 | $0.00986 |
| Opus 5.5 | $0.00025 | $0.00394 |
| Sonnet 5.5 | $0.00012 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
backend-deployment-safety-review 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Deployment Safety Review
Overview
Review backend changes for safe deployment in production: feature flag readiness for risky behavior changes, backwards-compatible evolution of public APIs and database schemas, rollback paths, blast-radius scoping, and correctness across multiple application instances.
Framework-agnostic: applies to any service that ships through a CD pipeline with rolling deploys, blue/green, or canary rollouts.
When to Use
- Reviewing changes that affect public API contracts
- Reviewing migration files (Flyway, Liquibase, Alembic)
- Reviewing config files / config beans / static toggles
- Pre-implementation: planning rollout strategy
When NOT to Use
- Internal scripts run once on a developer machine — different concerns
- Pure documentation / comment-only changes
- Operational deploy mechanics (Helm chart, K8s rollout strategy) — use kubernetes domain skills
Review Process
- Inventory: API contract changes, migration files, config files, beans with state
- For each, apply Evaluation Points S1–S10
- Cross-cut: ensure the change can roll back in <5 minutes; ensure two consecutive versions can run side-by-side
Evaluation Points
| # | Check | What to Look For | Severity |
|---|---|---|---|
| S1 | Feature flag for risky changes | Behavior changes that affect business logic gated behind a runtime flag with default-off | High |
| S2 | API backwards compatibility | Existing endpoints unchanged, OR new endpoints added alongside, OR Sunset/Deprecation headers + transition window | High |
| S3 | Schema migration safety | Adds are safe; column drops/renames use expand/contract pattern across two deploys; no data loss without explicit migration | High |
| S4 | Rollback path | Code change is reversible. If the migration is not reversible, the application code must tolerate the old schema for the rollback window | High |
| S5 | Blast radius | Change is scoped to a small set of users/tenants/endpoints first (canary, percentage rollout) when impact is uncertain | Medium |
| S6 | Multi-instance state safety | No process-local mutable state shared across requests in a multi-instance deploy. In-memory caches must be acknowledged and bounded; sticky sessions must be deliberate | High |
| S7 | Configuration externalization | Config that varies per environment lives in env vars / config server, not committed source | Medium |
| S8 | Migration ordering | Code that reads new schema deploys after migration; code that writes old schema deploys before drop migrations | High |
| S9 | Idempotent deploy hooks | Startup hooks, init containers, schema bootstrap can run multiple times safely | Medium |
| S10 | No global side effects on import | Importing a module / loading a class doesn't mutate the world (e.g., no DB writes in a static initializer) | Medium |
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 · 78 lines · 62 tokens per session scan A a423075ed6a2
backend-deployment-safety-review is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 986 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…