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/fo0/clawstash/cinpx skills add fo0/clawstash --skill cigit clone --depth 1 https://github.com/fo0/clawstashWhat 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.00080 | $0.01661 |
| Opus 5 | $0.00040 | $0.00830 |
| Sonnet 5 | $0.00016 | $0.00332 |
| Haiku 4.5 | $0.00008 | $0.00166 |
Grade A, and why
ci scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Jenkins: web UI, `curl <jenkins>/job/<name>/lastBuild/consoleText` How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI — Continuous Integration Workflow
When to Use
- After
git pushwhen CI may be running - User says "/ci", "CI status", "check the build", "fix CI", "why is CI red", "look at the build"
- Triaging a failing branch / PR before merging
Prerequisites
gh auth status && gh repo view --json name,owner
If gh is missing or unauthenticated, fall back to the GitHub MCP server before stopping (Claude Code web/remote
sessions have mcp__github__* but no CLI): actions_list / actions_get for runs and jobs, get_job_logs
(failed_only: true) for the failed-step logs Phase D needs, get_check_run for check details,
pull_request_read(method: "get_check_runs") for a PR's checks. Only when neither exists: print the install/login
instructions and stop. CI providers other than GitHub Actions: see "Other CI Providers" at the bottom.
Auto-Routing (default /ci)
BRANCH=$(git rev-parse --abbrev-ref HEAD)
HEAD_SHA=$(git rev-parse HEAD)
RUNS=$(gh run list --branch "$BRANCH" --limit 5 --json databaseId,status,conclusion,headSha,name,workflowName)
Decision matrix:
| State | Action |
|---|---|
| No runs found for branch | Phase A — report "no CI runs yet" |
Latest run still in_progress / queued |
Phase B — show running status |
Latest run success |
Phase C — green report |
Latest run failure / cancelled / timed_out |
Phase D — fetch logs + propose fix |
Latest run is for headSha != HEAD_SHA (stale) |
Phase E — note stale, run for prior SHA shown only on request |
Print detected phase before acting:
Detected: latest CI run failed (run #123, workflow "build"). Fetching failed-job logs.
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.
- yesterday First seen · 168 lines · 80 tokens per session scan A 1434cb22b7f0
ci is a skill published in the GitHub repository fo0/clawstash (1 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,661 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.