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 instructions/khrichtchatyi/ship-it/open-prgit clone --depth 1 https://github.com/khrichtchatyi/ship-itWrote 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/instructions/khrichtchatyi/ship-it/open-pr)<a href="https://agentmods.dev/instructions/khrichtchatyi/ship-it/open-pr"><img src="https://agentmods.dev/badge/instructions/khrichtchatyi/ship-it/open-pr.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.00084 | $0.00084 |
| Opus 5 | $0.00042 | $0.00042 |
| Sonnet 5 | $0.00017 | $0.00017 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
ship-it open-pr.instructions.md 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 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.
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.
What it actually says
When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the commits, and stop.
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 · 6 lines · 84 tokens per session scan A 940807b91f57
ship-it open-pr.instructions.md is an instructions file published in the GitHub repository khrichtchatyi/ship-it (2 stars, last pushed 21d ago), licensed MIT. It adds 84 tokens to every session, 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 instructions, from other repositories
dev-agent-skills CLAUDE.md
Instructions for fvadicamo/dev-agent-skills, covering claude.md, project overview, architecture, key file: marketplace.json and skill anatomy.
claude-code-gauntlet AGENTS.md
Instructions for liatrio-labs/claude-code-gauntlet, covering agents.md, design, tooling boundary (no npm in the tree), scripts and tests.
claude-code-gauntlet CLAUDE.md
Instructions for liatrio-labs/claude-code-gauntlet, covering claude.md and claude code specifics.
nyann CLAUDE.md
Claude Code instructions for thettwe/nyann, covering claude.md, architecture & conventions, skill authoring rules (apply to every skill.md) and scope reminders.
oss-scout CLAUDE.md
Claude Code instructions for costajohnt/oss-scout, covering claude.md, project overview, architecture, key design decisions and file structure.
claude-code-plugins CLAUDE.md
Instructions for zhebil/claude-code-plugins, covering claude.md, what this repo is, plugins, auto-enrich and common commands.