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/prnpx skills add fo0/clawstash --skill prgit 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.02919 |
| Opus 5 | $0.00040 | $0.01460 |
| Sonnet 5 | $0.00016 | $0.00584 |
| Haiku 4.5 | $0.00008 | $0.00292 |
Grade A, and why
pr 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 2d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR — Pull Request Workflow
When to Use
- User says "PR" / "/pr" / "create PR" / "open PR" / "update PR" -> auto-route by state
- User says "PR status" / "/pr status" / "check PR" -> status (override)
- User says "PR comments" / "/pr comments" -> read review comments (override)
- User says "merge PR" / "/pr merge" -> merge (explicit only, never automatic; owner-authorized routines count as explicit — see
/pr merge) - After done-skill push step on a feature branch -> suggested, user invokes
/prto trigger
Prerequisites
gh auth status && gh repo view --json name,owner
If gh is missing or unauthenticated, check for the GitHub MCP server before giving up -- Claude Code web/remote
sessions ship mcp__github__* tools instead of the CLI, and an unattended routine must not stall there:
| Available | Do this |
|---|---|
gh |
Use the commands as written below (preferred -- least round-trips) |
| GitHub MCP only | Same workflow, MCP equivalents: list_pull_requests / create_pull_request / update_pull_request / pull_request_read (get, get_status, get_comments, get_review_comments) / merge_pull_request. git push still runs over plain git |
| Neither | Print No GitHub access (gh CLI or GitHub MCP required). and stop -- do NOT fall back to manual PR creation via web |
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.
- 2d ago First seen · 207 lines · 80 tokens per session scan A 07d3a3ca2122
pr 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 2,919 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
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…
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
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…
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…
add-service
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.