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 skills add ronaknnathani/relay --skill deliver-prgit clone --depth 1 https://github.com/ronaknnathani/relayWrote 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/ronaknnathani/relay/deliver-pr)<a href="https://agentmods.dev/skills/ronaknnathani/relay/deliver-pr"><img src="https://agentmods.dev/badge/skills/ronaknnathani/relay/deliver-pr/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/ronaknnathani/relay/deliver-pr"><img src="https://agentmods.dev/badge/skills/ronaknnathani/relay/deliver-pr.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.00082 | $0.03222 |
| Opus 5 | $0.00041 | $0.01611 |
| Sonnet 5 | $0.00016 | $0.00644 |
| Haiku 4.5 | $0.00008 | $0.00322 |
Grade A, and why
deliver-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 5d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deliver PR
Drive one change from a task to an open PR by orchestrating the foundation skills, one phase at a time, with durable resumable state. You are a router, not a worker: you read state, dispatch the next phase as a sub-agent, record the result, and move on. You do not do the phase work yourself, and you stay context-light — you read digests and state, never file dumps.
Session goal
In every agent harness, set /goal to the user's requested outcome. The deliver-pr workflow is the
execution method, not the goal. Keep task.md, requirements, and relay state as the durable
definition and progress record across resumes.
Managed assignment — before state routing
Bind the invocation argument to $SLUG, then check
$HOME/.relay/projects/active/$SLUG/assignment.md. If it exists, read it completely before asking
relay state for the next phase. This is a managed program worker: the assignment's contracts and
escalation commands are binding, while the worker still owns independent clarify and plan work.
Bind the exact Program: and Work item: values from the assignment to $PROGRAM and $ITEM, then
run and read:
relay program message inbox <program> <item> --json
Use the exact program and item from the assignment in place of the placeholders. Act on every unread decision, feedback, or instruction before state routing. Acknowledge each message only after its requested action or resulting state/artifact update is durable:
relay program message ack <program> <item> <inbox-id>
An open-PR grant instruction is the exception: keep it unread until open-pr succeeds and the PR is
recorded. If open-pr fails, do not acknowledge the grant.
A feedback message about a change the CEO asked for on your open pull request is work, not review
chatter: make the change on the branch and pull request you already have. Never open a second pull
request for this item and never start unrelated work from it. Acknowledge it once the change is
pushed.
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.
- 5d ago Changed · +110 lines c2becee78b39
- 10d ago First seen · 112 lines · 82 tokens per session scan A 84c651810f2d
deliver-pr is a skill published in the GitHub repository ronaknnathani/relay (3 stars, last pushed 7d ago), licensed MIT. It adds 82 tokens to every session and 3,222 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
conventional-commit
Generer conventional commit-meldinger med Nav-relevante scopes og breaking change-format.
security-ownership-map
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Use when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example…
gh-address-comments
Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging…
repo-status
Checks the status of the repository.
repo-status
Checks the status of the repository.
git-ops
Safe git operations including commits, branches, merges, worktrees, and conflict resolution. Use when user wants to commit and push changes, manage branches, resolve conflicts, or create isolated workspaces. Activates when user says "commit", "push", "merge", "branch", "pull", "rebase", "worktree", "conflict", or…