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 ivanhoinacki/team-exp-claude-config --skill deploy-checklistgit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/ivanhoinacki/team-exp-claude-config/deploy-checklist)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/deploy-checklist"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/deploy-checklist/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/ivanhoinacki/team-exp-claude-config/deploy-checklist"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/deploy-checklist.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.00088 | $0.02634 |
| Opus 5.5 | $0.00035 | $0.01054 |
| Sonnet 5.5 | $0.00018 | $0.00527 |
| Haiku 4.5 | $0.00009 | $0.00263 |
Grade A, and why
deploy-checklist scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- For each endpoint, generate a curl command for staging How it starts
The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Vault RAG (MANDATORY, BEFORE any Read/Grep)
You MUST call query_vault(query, service_filter) BEFORE reading codebase files or external sources. This is enforced by hook. No exceptions.
Deploy Checklist Generator
Working Directories
- Obsidian workspace (docs, plans, features):
__VAULT_ROOT__ - Codebase (all LE services):
__CODEBASE_ROOT__
Generate a deployment checklist based on the actual changes in the current branch.
References
references/checklist-sections.md- Section templates, inclusion rules, monitoring linksreferences/risk-matrix.md- Risk factor matrix and deploy strategiesreferences/learnings.md- Lessons from past deployments (review before generating)
Phase 1: Collect Context
# Branch and commit info
GIT_EDITOR=true git branch --show-current
GIT_EDITOR=true git log main..HEAD --oneline
GIT_EDITOR=true git diff main...HEAD --name-only
GIT_EDITOR=true git diff main...HEAD --stat
Identify the ticket number from $ARGUMENTS or from the branch name (e.g., feat/EXP-3500-description -> EXP-3500).
Read references/learnings.md for any relevant lessons from past deployments.
Phase 2: Parallel Analysis (subagents)
Launch 2 subagents in parallel to analyze the branch changes:
Agent 1: Infrastructure and Config Analysis
Analyze the git diff (main...HEAD) for infrastructure and configuration changes:
1. ENV VARS - Search for:
- New `process.env.*` references in the diff
- Changes to Pulumi YAML files (Pulumi.staging.yaml, Pulumi.prod.yaml)
- Changes to environment-variables.ts, config files, schema files
- For each new env var, trace the 4-layer chain:
a) Pulumi YAML (value present in BOTH staging and prod?)
b) environment-variables.ts (mapped?)
c) config/index.ts (exported?)
d) config/schema.ts (validated?)
- Report any breaks in the chain
2. SECRETS - Check for:
- New entries in secretNames[] array
- New `secure:` entries in Pulumi YAMLs
- Missing secrets (referenced in code but not in Pulumi config)
3. FEATURE FLAGS - Check for:
- Env vars with ENABLED/FEATURE/FLAG in the name
- Current values in staging vs prod YAMLs
4. DEPENDENCIES - Check for:
- package.json changes (new deps, version bumps, removed deps)
- Lock file changes
Return: env var chain report, secrets list, feature flags, dependency changes.
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.
- 2mo ago First seen · 323 lines · 88 tokens per session scan A 933e061ae2bc
deploy-checklist is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 26d ago), licensed MIT. It adds 88 tokens to every session and 2,634 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
updater_guide
Is Row-Bot up to date? Checking for and installing Row-Bot updates.