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/shipwithai/shipwithai-plugins/setup-observabilitynpx skills add ShipWithAI/shipwithai-plugins --skill setup-observabilitygit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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/shipwithai/shipwithai-plugins/setup-observability)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/setup-observability"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/setup-observability.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.00057 | $0.00823 |
| Opus 5 | $0.00028 | $0.00411 |
| Sonnet 5 | $0.00011 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade B, and why
setup-observability 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 3d 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.
"hooks": [{"type": "command", "command": "find .claude/logs -name '*.jsonl' -mtime +30 -delete 2>/dev/null || true"}] How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-observability
Installs a lightweight logging hook that records tool call metadata. Logs feed future harness analysis tooling (coming in a later phase).
What gets logged
Only metadata — never content:
| Tool | Logged | NOT logged |
|---|---|---|
| Edit | Relative file path | File content, old/new string |
| Write | Relative file path | File content |
| Bash | Command name (argv[0] only) | Arguments, output, exit code |
One line per call: .claude/logs/YYYY-MM-DD.jsonl
Opt-out anytime: export DISABLE_OBSERVE=1 in terminal or shell profile.
Mode Detection
--disable flag → reverse setup (see --disable Flow below)
No args → run setup flow
Setup Steps
- Copy
observe.pyfrom plugin assets to.claude/hooks/observe.py - Merge PostToolUse hook into
.claude/settings.json— matcherEdit|Write|Bash - Merge Stop hook (log rotation) into
.claude/settings.json - Add
.claude/logs/to.gitignore(skip if already present) - Check
git ls-files .claude/logs— warn user if currently tracked - Update
starter-context.json→observability.enabled: true
Output Format
Preview before writing:
Observability setup:
.claude/hooks/observe.py CREATE
.claude/settings.json (hook) UPDATE — add PostToolUse + Stop entries
.gitignore UPDATE — add .claude/logs/
Logs will be written to: .claude/logs/YYYY-MM-DD.jsonl
Opt-out: export DISABLE_OBSERVE=1
Proceed?
After writing:
✅ Observability enabled.
Logs: .claude/logs/ (excluded from git)
Disable anytime: export DISABLE_OBSERVE=1
Logs will feed harness analysis tooling (coming in a future phase).
settings.json Hook Entries
PostToolUse entry to add:
{
"matcher": "Edit|Write|Bash",
"hooks": [{"type": "command", "command": "python3 .claude/hooks/observe.py"}]
}
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.
- 3d ago First seen · 102 lines · 57 tokens per session scan B 16ce861445c2
setup-observability is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 21d ago), licensed MIT. It adds 57 tokens to every session and 823 once invoked, about $0.0003 per session on Opus 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
alipay-webhooks
Receive and verify Alipay (Antom / Alipay+) webhook notifications. Use when setting up Alipay webhook handlers, debugging RSA256 Signature header verification, or handling payment events like notifyPayment, notifyCapture, notifyRefund, notifyAuthorization, and notifyDispute.