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/shipwrights/core/shipwrights-connectnpx skills add shipwrights/core --skill shipwrights-connectgit clone --depth 1 https://github.com/shipwrights/coreWrote 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/shipwrights/core/shipwrights-connect)<a href="https://agentmods.dev/skills/shipwrights/core/shipwrights-connect"><img src="https://agentmods.dev/badge/skills/shipwrights/core/shipwrights-connect.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.00071 | $0.01837 |
| Opus 5 | $0.00036 | $0.00919 |
| Sonnet 5 | $0.00014 | $0.00367 |
| Haiku 4.5 | $0.00007 | $0.00184 |
Grade A, and why
shipwrights-connect 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 4d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shipwrights-connect — wire a backlog source into the project
Takes a fresh .shipwrights.yml from source: { kind: files } (the default after /shipwrights-init) to a fully connected external source — without the user hand-editing YAML, hand-rolling JQL, or chasing down custom-field IDs.
Pairs with the source package's CLI wizard. The wizard handles the secret-bearing connection step (token masked locally); this skill handles everything around it: detection, install, config merging, commit, validation.
Inputs
/shipwrights-connect— interactive picker (asks which source)./shipwrights-connect jira— go directly to Jira./shipwrights-connect github— github-issues (stubbed; depends on@shipwrights/source-github-issueswhich is not yet shipped)./shipwrights-connect files— switch to local files mode (no wizard needed).
Workflow for Jira
1. Preflight
Check, in order:
.shipwrights.ymlexists. If not: stop, tell user to run/shipwrights-initfirst.- Working tree clean for the files you're about to touch (
.shipwrights.yml,.shipwrights/jira.json,.gitignore,.env.local). Other unrelated dirty files are fine. Refuse if any target file has uncommitted changes the user hasn't acknowledged. @shipwrights/source-jirais reachable. Trynpx --no-install @shipwrights/source-jira --version. If it errors, ask the user via AskUserQuestion: "Install@shipwrights/source-jiraas a devDep?" Detect their package manager from lockfiles (yarn.lock→yarn add -D,pnpm-lock.yaml→pnpm add -D, otherwisenpm install -D).
2. Run the source's wizard
If .shipwrights/jira.json already exists, ask via AskUserQuestion:
- "Use existing config" — skip to step 3.
- "Re-run setup" — delete
.shipwrights/jira.jsonand proceed.
Otherwise, tell the user to run the wizard in their terminal. Use the ! prefix convention so the command lands in their shell:
! npx @shipwrights/source-jira init
Explain that the token is masked in the terminal but won't be visible in this chat. Wait for them via AskUserQuestion: "Wizard finished cleanly?"
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.
- 4d ago First seen · 143 lines · 71 tokens per session scan A 500aeed465a2
shipwrights-connect is a skill published in the GitHub repository shipwrights/core (2 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,837 once invoked, about $0.0004 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
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
cost-model
Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.
migration-ready-schema
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Every SMB Product-Builder product must let a customer bring their data from an incumbent (ServiceTitan/Toast/Mindbody/Shopify) — that requires provenance (sourceref) and rollback…
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…