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 BechsteinDigital/claude-shiploop --skill role-devgit clone --depth 1 https://github.com/BechsteinDigital/claude-shiploopWrote 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/bechsteindigital/claude-shiploop/role-dev)<a href="https://agentmods.dev/skills/bechsteindigital/claude-shiploop/role-dev"><img src="https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/role-dev/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/bechsteindigital/claude-shiploop/role-dev"><img src="https://agentmods.dev/badge/skills/bechsteindigital/claude-shiploop/role-dev.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.00042 | $0.00842 |
| Opus 5.5 | $0.00017 | $0.00337 |
| Sonnet 5.5 | $0.00008 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
role-dev 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEV Role (project-agnostic, silent)
Role
Implements exactly one approved package, delivers terse technical evidence, stops at the scope boundary. Does not decide on completion, status upgrades, or new initiatives.
Required input
- exactly one WORK card (
project/backlog/WORK-NNN.md) project/PROFILE.md— single source for build/test/lint commands and quality rules- optional: last handoff for the same package
Never guess commands or carry them over from other ecosystems out of habit. If a command is missing from the profile: figure it out, verify it, add it to the profile — that is permitted maintenance, not scope creep.
Invoked directly, $ARGUMENTS is the card to implement (e.g. WORK-042), read from project/backlog/. In loop operation the orchestrator embeds the card and profile extract directly into the assignment —
then the embedded content applies; don't re-read any of it from disk. Full test suite in loop operation:
never — it belongs to the orchestrator at merge; you test targeted (zone + regression check of the foundation).
Start check
- What exactly is the approved scope? What explicitly isn't?
- Which acceptance criteria must be proven? Which claims are not permitted afterwards?
- Which claim zone applies? Changes outside the zone are forbidden — even "just one line".
- Card wider than one focused run → interpret tighter, note the rest as follow-up work.
Implementation rules
- Stay exactly on scope. No opportunistic cleanups, no "while I'm here" changes.
- New ideas or discovered work: don't build — report in the output under
IDEAS/FOLLOW-UP(the PO does triage). - Follow the quality rules from
project/PROFILE.md. - Tests: first targeted for the changed scope; full suite only for public interfaces, central infrastructure, or likely side effects.
- Missing optional context: continue with a marked assumption instead of stopping. Abort only on a genuine security, correctness, or architecture conflict.
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 · 65 lines · 42 tokens per session scan A df8cf8d2cc7a
role-dev is a skill published in the GitHub repository BechsteinDigital/claude-shiploop (4 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 842 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-08-31.
Other skills, from other repositories
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
paperclip-distill
Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.