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/stefan-stepzero/shipkit/shipkit-communicationsnpx skills add stefan-stepzero/shipkit --skill shipkit-communicationsgit clone --depth 1 https://github.com/stefan-stepzero/shipkitWhat 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.00035 | $0.03565 |
| Opus 5 | $0.00017 | $0.01783 |
| Sonnet 5 | $0.00007 | $0.00713 |
| Haiku 4.5 | $0.00003 | $0.00357 |
Grade A, and why
shipkit-communications 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 2d 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 — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shipkit-communications - Visual HTML Reports
Purpose: Create beautiful, visual HTML reports from any ShipKit Lite content for presentations, sharing, or visual review.
What it does: Reads markdown content from .shipkit/, generates styled HTML with purple gradient theme, archives old reports, creates latest.html.
When to Invoke
User triggers:
- "Visualize the architecture decisions"
- "Create HTML report"
- "Make a visual status report"
- "Generate presentation from project status"
- "Show me quality checklist as HTML"
- "Create shareable report"
Use cases:
- Share architecture decisions with team
- Present project status to stakeholders
- Visual review of quality checklist
- Export component documentation as HTML
- Create visual specs for review
Prerequisites
Optional (depends on what user wants to visualize):
.shipkit/architecture.json- For architecture decisions.shipkit/codebase-index.json- For component/route docs.shipkit/stack.json- For tech stack overview.shipkit/specs/{todo,active}/*.json- For specs.shipkit/plans/{todo,active}/*.json- For implementation plans
No strict prerequisites - Can create HTML from any content.
Process
Step 1: Ask What to Visualize
Before generating anything, ask user what they want to visualize:
Present options:
What would you like to visualize as HTML?
1. Architecture Decisions - Visual timeline of decisions
2. Project Status - Complete health dashboard
3. Quality Checklist - Pre-ship verification
4. Component Documentation - All components/routes
5. Feature Specs - Active specifications
6. Implementation Plans - Current plans
7. Tech Stack - Visual stack overview
8. Custom - You specify the files
Choose a number or describe what you need:
Wait for user response.
Step 2: Determine Source Files
Based on user choice, identify which .shipkit/ files to read:
| Choice | Files to Read | Description Word |
|---|---|---|
| 1. Architecture Decisions | .shipkit/architecture.json |
architecture-decisions |
| 2. Project Status | Glob .shipkit/**/*.json |
project-health |
| 3. Quality Checklist | .shipkit/codebase-index.json, .shipkit/specs/{todo,active}/*.json |
quality-checklist |
| 4. Component Documentation | .shipkit/codebase-index.json |
component-docs |
| 5. Feature Specs | .shipkit/specs/{todo,active}/*.json |
feature-specs |
| 6. Implementation Plans | .shipkit/plans/{todo,active}/*.json |
implementation-plans |
| 7. Tech Stack | .shipkit/stack.json |
tech-stack |
| 8. Custom | User-specified files | User-specified description |
What ships with it
1 file 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.
- 2d ago First seen · 533 lines · 35 tokens per session scan A 8227bda670f0
shipkit-communications is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 3,565 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-buzz
This is a Hermes-native buzz workflow skill.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
redteam-postex-detail-pack
Domain routing and boundary guidance for authorized post-exploitation testing after initial access, including privilege escalation, persistence, lateral movement, data collection, and cleanup considerations. Use when a task belongs to the post-exploitation domain and needs scope, evidence, pivot, or exit criteria.