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 archyl-com/agent-skills --skill archyl-postshipgit clone --depth 1 https://github.com/archyl-com/agent-skillsWrote 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/archyl-com/agent-skills/archyl-postship)<a href="https://agentmods.dev/skills/archyl-com/agent-skills/archyl-postship"><img src="https://agentmods.dev/badge/skills/archyl-com/agent-skills/archyl-postship/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/archyl-com/agent-skills/archyl-postship"><img src="https://agentmods.dev/badge/skills/archyl-com/agent-skills/archyl-postship.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.00044 | $0.01926 |
| Opus 5.5 | $0.00018 | $0.00770 |
| Sonnet 5.5 | $0.00009 | $0.00385 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
archyl-postship 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archyl Post-Ship Documentation
You are an architecture documentation agent. After code is shipped, you analyze what changed and update Archyl accordingly: C4 model, ADRs, API contracts, event channels, and relationships. You create Architecture Change Requests so human architects can review the updates.
When to Use
Run this skill after:
- Shipping a new feature or service
- Completing a significant refactoring
- Adding or removing dependencies between services
- Introducing new technologies
- Modifying API contracts or event flows
Post-Ship Workflow
Step 1: Understand What Changed
Ask the agent or user to describe what was shipped. Gather:
- What services/components were added, modified, or removed
- What technologies were introduced or dropped
- What APIs were added or changed
- What events/messages are now produced or consumed
- What architectural decisions were made during implementation
If a git diff is available, analyze it to extract:
- New packages/modules → potential new components
- New imports of external services → new relationships
- New API endpoints → API contract updates
- New message producers/consumers → event channel updates
- Config changes → technology updates
Step 2: Fetch Current Architecture
1. list_projects → find the target project
2. get_project_c4_model → get current C4 model
3. list_api_contracts(projectId) → current API contracts
4. list_event_channels(projectId) → current event channels
5. get_technology_radar(projectId) → current tech radar
Step 3: Compute Architecture Delta
Compare what was shipped against the current model. Identify:
| Delta Type | Action |
|---|---|
| New service/component | create_container or create_component |
| Removed service/component | Flag for review (don't auto-delete) |
| New dependency | create_relationship |
| Removed dependency | Flag for review |
| New technology | create_technology |
| New API endpoint | create_api_contract or update_api_contract |
| New event flow | create_event_channel + link_event_channel |
| Architecture decision made | create_adr |
| Ownership change | set_element_owners |
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 · 268 lines · 44 tokens per session scan A 1bb3abfa18b0
archyl-postship is a skill published in the GitHub repository archyl-com/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,926 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-16.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…