Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add 3awny/qship/plugin install qshipWrote 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/3awny/qship/configure)<a href="https://agentmods.dev/skills/3awny/qship/configure"><img src="https://agentmods.dev/badge/skills/3awny/qship/configure/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/3awny/qship/configure"><img src="https://agentmods.dev/badge/skills/3awny/qship/configure.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.00126 | $0.02785 |
| Opus 5.5 | $0.00050 | $0.01114 |
| Sonnet 5.5 | $0.00025 | $0.00557 |
| Haiku 4.5 | $0.00013 | $0.00279 |
Grade B, and why
configure scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
4. **Shells out to `setup.sh --config <answers-file>`** to render templates via `envsubst`, write `repos.json` to the skill root, merge hooks into `~/.claude/settings.json`, and touch the first-run marker. How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qship — interactive configurator
This skill is the bootstrap step for the qship plugin. The plugin ships templates; this skill collects the values that fill them in.
When to run
- First time you install the qship plugin — the SessionStart hook prints a prompt directing you here.
- Whenever you want to change a configured value — added a service, new Jira project key, opted into a previously-skipped integration (Alembic migrations, ngrok, Playwright). Re-running re-renders the whole catalog from the latest answers.
What it does, end-to-end
- Loads previous answers from
$CLAUDE_PLUGIN_ROOT/answers/last-run.jsonif present. - Asks the questionnaire (7 rounds, ~two dozen questions) plus a per-repo loop via the
AskUserQuestiontool. Defaults pulled from$HOME,git config,$USER, and platform conventions wherever possible. - Writes the consolidated answers to
$CLAUDE_PLUGIN_ROOT/answers/last-run.json. - Shells out to
setup.sh --config <answers-file>to render templates viaenvsubst, writerepos.jsonto the skill root, merge hooks into~/.claude/settings.json, and touch the first-run marker. - Verifies the install via
setup.sh --checkand surfaces any missing external plugins to the user. - Prints a quickstart with example invocations.
Step-by-step
Step 1 — Load previous answers, if any
ANSWERS_FILE="$CLAUDE_PLUGIN_ROOT/answers/last-run.json"
mkdir -p "$(dirname "$ANSWERS_FILE")"
if [ -f "$ANSWERS_FILE" ]; then
echo "[/qship:configure] Loaded previous answers from $ANSWERS_FILE."
fi
Use the values from $ANSWERS_FILE as the per-question default in the next step.
Step 2 — Auto-detect what you can
USER_HOME="${USER_HOME:-$HOME}"
SKILLS_ROOT="${SKILLS_ROOT:-$HOME/.claude/skills}"
LOCAL_DB_USER_DEFAULT="${LOCAL_DB_USER:-$USER}"
GH_HOST_DEFAULT="${GH_HOST:-github.com}"
DEFAULT_BRANCH_DEFAULT="${DEFAULT_BRANCH:-develop}"
PRIMARY_LANGUAGE_DEFAULT="${PRIMARY_LANGUAGE:-python}"
CODEBASE_ROOT_DEFAULT="${CODEBASE_ROOT:-$(git -C "$PWD" rev-parse --show-toplevel 2>/dev/null || echo "$HOME/work/your-monorepo")}"
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 · 186 lines · 126 tokens per session scan B e0ebf1c02124
configure is a skill published in the GitHub repository 3awny/qship (2 stars, last pushed 3mo ago), licensed MIT. It adds 126 tokens to every session and 2,785 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memory
Activate this skill when starting a new session, beginning a new task, saving knowledge, recalling past decisions, or after completing significant work. Also activate on errors to log them for pattern analysis. Relevant when the user asks about memory, past context, lessons learned, decisions history, project…
design-explore
Explore 2-4 design options with pros/cons/criteria matrix before writing code. Use for L3-L4 tasks (refactors, architecture, new subsystems). Pairs with savedecision MCP tool.
onboard
Department onboarding for a new employee on the total-agent-memory team server. Use when the user types /onboard, asks to be onboarded, trained, or introduced to a department/team, wants to continue their training, take the department quiz, or see their onboarding progress. Requires the team server MCP tools…
report
Activity report from total-agent-memory for a project and period. Use when the user types /report or asks "report for today", "what did we do this week", "weekly / monthly summary", "status report", "retro for project X", "all-time report", "report for last week", or a report for a department or the whole company on…
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.