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 agentmods add skills/jazzyalex/agent-sessions/deploynpx skills add jazzyalex/agent-sessions --skill deploygit clone --depth 1 https://github.com/jazzyalex/agent-sessionsWrote 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/jazzyalex/agent-sessions/deploy)<a href="https://agentmods.dev/skills/jazzyalex/agent-sessions/deploy"><img src="https://agentmods.dev/badge/skills/jazzyalex/agent-sessions/deploy.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.03158 |
| Opus 5 | $0.00018 | $0.01579 |
| Sonnet 5 | $0.00007 | $0.00632 |
| Haiku 4.5 | $0.00004 | $0.00316 |
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 today.
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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Skill (Agent Sessions)
This skill is an agent-facing entrypoint that avoids duplicating the deployment runbook.
Canonical Sources (Single Source of Truth)
- Runbook:
docs/deployment.md - Unified tool:
tools/release/deploy(seetools/release/deploy --help) - Recommended pre-release QA checklist:
docs/release/pre-release-qa.md
If anything here disagrees with the runbook, follow docs/deployment.md.
Workspace Policy (Hard Rule)
- Always run deployment from the user's current local repository checkout.
- Do not clone to temporary directories and do not switch to alternate worktrees as a deployment workaround.
- If the local worktree is dirty, stop and tell the user to clean the tree first (commit, stash, or discard), then continue in the same local repo.
QA Gate (Mandatory — Run Automatically Before Deploy)
- Always run QA automatically before any bump/release/verify step, unless the user explicitly says to skip it (e.g. "skip QA", "no QA").
- Do not ask whether to run QA — just run it.
- QA execution order:
- Scope —
git log --oneline --decorate -n 30andgit diff --name-only <LAST_TAG>..HEAD; identify high-risk areas. - Build —
xcodebuild -project AgentSessions.xcodeproj -scheme AgentSessions -configuration Debug build - Full test suite —
./scripts/xcode_test_stable.sh - Targeted tests — run suites for touched high-risk areas (session parsing, usage tracking, onboarding, etc.)
- Warnings sweep — flag any new actionable warnings in build output.
- Manual smoke reminder — list the manual steps from
docs/release/pre-release-qa.md§3–4 and ask the user to confirm GO/NO-GO after completing them.
- Scope —
- If automated gates fail → stop, report failure, do not proceed to bump/release.
- If user says "skip QA" or "no QA" → proceed without running, note it was skipped.
Test count. QA reads the authoritative pass count from the .xcresult bundle (stdout
reports per-bundle totals and this scheme has two — it under-reports) and compares it to
tools/release/test-count-baseline.txt. A drop warns and continues, deliberately: it
does not block a release. So the warning has to actually be read — a deleted suite still
exits 0 from xcodebuild, and this line is the only thing that says so. When the count
changes for a real reason, update the baseline file in the same release.
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.
- today Changed · +46 lines 2df43a774c12
- 4d ago First seen · 163 lines · 37 tokens per session scan A 0cf4e54dca5a
deploy is a skill published in the GitHub repository jazzyalex/agent-sessions (842 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 3,158 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
kirby-collections-and-navigation
Builds Kirby listings, pagination, search, filtering/sorting/grouping, and navigation menus. Use when implementing collection logic in templates/controllers/snippets.
kirby-routing-and-representations
Implements custom Kirby routes and content representations (.json/.xml/.rss), including redirects, sitemap endpoints, and URL pattern filtering. Use when building endpoints, redirects, or representation templates that change how URLs resolve.
kirby-scaffold-page-type
Scaffolds a new Kirby page type (blueprint + template, optional controller/model) using project roots, index tools, and Panel field/section references. Use when creating a new page type or extending an existing blueprint/template.
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.
kirby-forms-and-frontend-actions
Implements frontend forms and actions in Kirby (contact forms, file uploads, email with attachments, creating pages from frontend). Use when handling user input or building submission flows.
kirby-headless-api
Exposes Kirby content to headless clients using the API, KQL, and JSON representations. Use when building API endpoints, KQL queries, or headless frontends.