keystone: Agent for Claude Code

.claude/agents/keystone-review-deployment.md

keystone-review-deployment is an agent for Claude Code from tacoda/keystone. It costs 31 tokens per session (261 once invoked), scanned A, a copy of review-deployment, MIT.

A deployment review agent that examines code changes for risks when releasing them. It checks database changes, feature flags, configuration, rolling deployments, compatibility, and rollback plans.

In plain words
What is it for?
Use it during code review to assess schema migrations, environment drift, staged rollouts, backward compatibility, feature-flag use, and recovery paths.
Why use it?
It helps prevent releases that work in one environment but fail during migration or rollback. It makes deployment-specific blockers visible before the change ships.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is tacoda/keystone's own configuration. It tells Claude Code how to work on keystone itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything keystone configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tacoda/keystone. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tacoda/keystone/main/.claude/agents/keystone-review-deployment.md
Clone the repo
git clone --depth 1 https://github.com/tacoda/keystone

Made for: Claude Code.

Wrote 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.

agentmods badge for keystone-review-deployment

README.md
[![agentmods](https://agentmods.dev/badge/agents/tacoda/keystone/keystone-review-deployment/github.svg)](https://agentmods.dev/agents/tacoda/keystone/keystone-review-deployment)
Your own site
<a href="https://agentmods.dev/agents/tacoda/keystone/keystone-review-deployment"><img src="https://agentmods.dev/badge/agents/tacoda/keystone/keystone-review-deployment/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.

agentmods 80×15 button for keystone-review-deployment

Your own site · 80×15
<a href="https://agentmods.dev/agents/tacoda/keystone/keystone-review-deployment"><img src="https://agentmods.dev/badge/agents/tacoda/keystone/keystone-review-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 261 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod 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.1 $0.00031 $0.00261
Opus 5.5 $0.00012 $0.00104
Sonnet 5.5 $0.00006 $0.00052
Haiku 4.5 $0.00003 $0.00026

Measured 1mo ago against content hash 23e47293a0f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

keystone-review-deployment 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.

Origin

This is a copy

95% identical to review-deployment — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/keystone-review-deployment.md · 19 lines

What it actually says

Sensor: review-deployment

An agent reads the diff and reports deployment considerations — schema migration safety (expand-contract), feature-flag gating, environment / config drift, backwards compatibility during rolling deploy, the rollback path.

  • Trigger — review (review phase).
  • Inputs — the diff, the spec, and relevant deployment-sensitive corpus (e.g., corpus/principles/migrations.md, corpus/principles/rollback.md).
  • Exit condition — no blocking findings, or the user explicitly accepts the deployment risk.
  • Output — findings list keyed by file and line, each tagged blocking / nit / note, with the deployment concern referenced (schema, flag, config, compatibility, rollback).
  • State writes — none.

How the agent is invoked is adapter-specific — sub-agent, separate session, MCP tool, or a checklist prompt — see .charter/adapters/<your-agent>/sensors.md. The bootstrap action records whether this sensor is available for the project's active adapter.

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. 1mo ago First seen · 19 lines · 31 tokens per session scan A 23e47293a0f0

Subscribe to this mod's changes

keystone-review-deployment is an agent published in the GitHub repository tacoda/keystone (44 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 261 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to review-deployment, differing in 7 lines, and is treated as a copy.

Related

Other agents, from other repositories

vercel-reviewer

Vercel platform code review specialist — vercel.json config, Functions (Node.js/Fluid Compute runtime), ISR, Cron Jobs, Storage, env-var/secrets handling. Framework-agnostic (not Next.js-specific).

TheBeardedBearSAS/claude-craft · 50 tokens

cloud_architect

Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…

josstei/maestro-orchestrate · 83 tokens

mlops_engineer

MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…

josstei/maestro-orchestrate · 76 tokens

site_reliability_engineer

Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service…

josstei/maestro-orchestrate · 87 tokens

cloud-architect

Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…

josstei/maestro-orchestrate · 83 tokens

nw-platform-architect-reviewer

Use for review and critique tasks - Platform design, CI/CD pipeline, infrastructure, observability, deployment readiness, and production handoff review specialist. Runs on Haiku for cost efficiency.

nWave-ai/nWave · 44 tokens